Continuent is pleased to announce that Tungsten Clustering 5.3.6 and Tungsten Replicator 5.3.6 are now available!
Our 5.3.6 release fixes a number of bugs and has been released to improve stability.
Highlights common to both products:
Continuent is pleased to announce that Tungsten Clustering 5.3.6 and Tungsten Replicator 5.3.6 are now available!
Our 5.3.6 release fixes a number of bugs and has been released to improve stability.
Highlights common to both products:
Continuent is pleased to announce that Tungsten Clustering 6.0.4 and Tungsten Replicator 6.0.4 are now available!
Our v6.0.4 release fixes a number of bugs and introduces some new features, with improvements across the board in a variety of different components.
Some of the key improvements include:
Continuent is pleased to announce that Tungsten Clustering 5.3.4 and Tungsten Replicator 5.3.4 are now available!
Continuent is pleased to announce that Tungsten Dashboard v1.0.1 is now available!
Our Dashboard v1.0.1-36 is a bug fix release that also contains a few improvements. Some of the highlights include:
Continuent is pleased to announce that Tungsten Clustering 6.0.3 and Tungsten Replicator 6.0.3 are now available!
Continuent is pleased to announce that Tungsten Clustering 6.0.2 and Tungsten Replicator 6.0.2 are now available!
Our 6.0.2 release is a critical bug fix for the cluster Manager logic within a Multimaster cluster.
All current users of v6.0.0 and v6.0.1 should upgrade IMMEDIATELY!
Fixes issue CT-672: the manager could set the master to read-only when performing a switch operation.
There is a procedural work-around if you get into this situation:
Continuent is pleased to announce that Tungsten Clustering 5.3.2 and Tungsten Replicator 5.3.2 are now available!
We are pleased to announce that Tungsten Clustering 6.0.1 and Tungsten Replicator 6.0.1 are now available!
Over the years, Tungsten Clustering has grown and matured. Early on, in response to our customers' needs, we introduced the concept of the Passive Witness to allow for clusters with only two nodes. Normally, a cluster requires three nodes to create a voting quorum, which requires an odd number of members to avoid split-brain scenarios. It is the Witness which provides the tie-breaker in the event of a network partition.
We have identified an issue in a script that is executed as part of the Tungsten Clustering solution. The script itself executes a small query against the internal tables used by the replicator in order to help identify the current status and latency of the replication process.
Continuent is pleased to announce a brand new product, Tungsten Dashboard, which provides web-based UI to our Tungsten Clustering product.
Continuent are pleased to announce that the new 5.3.1 release is now available for all our customers.