Blog

We are pleased to announce the release of Tungsten Clustering and Tungsten Replicator v7.0.3, which includes several bug fixes, behavior changes, and new features. In this release, we have focused on improving the overall functionality of the product.

It may seem arduous, but there are ways to build a database stack where you have full control of your data and data operations. For mission-critical applications that must perform continuously 24/7/365, it might make a lot of sense to consider, as there are many benefits to taking control of your mission-critical data and operations. Below are a couple important points to consider when doing an analysis of what’s best for your application and end users.

The Tungsten Connector proxy within a Tungsten Cluster is a very powerful tool, able to route traffic many different ways. The Quality Of Service (QoS) determines where the Connector proxy will send client request packets, either to the Primary for writes or to a Replica for reads. This short blog post will show you how to use the command line to control the Quality Of Service when creating a new connection to the MySQL Server database.

In this blog post, we cover the correct method for doing Tungsten software upgrades. When doing systems and database administration, there are often multiple ways to get the job done. While each of those ways may work, there is often one way that is called the “best practice”, meaning that it is the agreed-upon best workflow to accomplish that specific goal. With Tungsten Clustering software, the same holds true.

VMware chose to migrate key MySQL database from Galera (MariaDB Cluster) to Tungsten. In this blog we will look at the key reasons for why VMware ultimately decided that Tungsten Cluster would better fit their multi-site MySQL clusters.

In this blog, part 5 of a series of “Recently a Customer Asked” posts for Tungsten University, we explore the values of the STATE output field in cctrl> ls which tells us about the health of the datasource. Specifically, we focus on the SHUNNED state, the different cctrl> ls outputs you may see when SHUNNED, and possible recovery steps.

One of the great powers of the Tungsten Cluster is that the writable Primary role can be moved to another node or cluster at will. When dealing with composite clusters and moving the Primary to another site entirely, there are different actions to take depending on the topology. In this blog post we will compare the procedures for moving the Primary role from one Composite cluster to another peer Composite cluster.

In this blog, part 4 of a series of “Recently a Customer Asked” posts for Tungsten University, we explore the purpose of the STATUS field in the cctrl> ls output and how it compares to the previous output.

In this blog, Continuent’s CEO and Founder, Eero Teerikorpi, was prompted by a headline in the Finnish News to write about the MySQL and MariaDB business and ecosystem.

We are pleased to announce that Tungsten Dashboard v1.0.13 is now available. Tungsten Dashboard is a web-based UI for monitoring and managing Tungsten Clustering deployments of MySQL databases, freely included for Tungsten Clustering customers. We provide Tungsten Dashboard in addition to our command-line user interfaces for easy visual monitoring and management of Tungsten Clusters. Users are able to view, monitor and maintain all of their database clusters in one place.

When was the last time you had an Urgent Support Request related to your MySQL deployment for your MySQL support or MySQL consulting provider? How fast were they able to come back to you? And was this by someone who actually could help you, or just a call center acknowledging your request?

Did you ever wonder just what the Tungsten Manager is thinking when it does an automatic failover or a manual switch in a cluster? What factors are taken into account by the Manager when it picks a replica to fail over to? This blog post will detail the steps the Manager takes to perform a switch or failover. We will cover both the process and some possible reasons why that process might not complete, along with best practices and ways to monitor the cluster for each situation.