Blog

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.

We are pleased to announce that Tungsten Dashboard v1.0.12 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.

In this blog, part 3 of a series of “Recently a Customer Asked” posts for Tungsten University, we explore the question: "Why does the tprovision command fail with error “Can’t connect to local MySQL server through socket” when using the xtrabackup method?

Running highly-available WordPress is especially challenging, because WordPress is not by nature Active/Active-aware, and will refuse to run in an environment where database writes are active-active. In this blog post Part 1, we will explore the design considerations for making WordPress highly-available at the database layer. We also cover some other WordPress HA architecture needs, like the need for a shared filesystem.

The purpose of the cctrl command is to provide easy access to the Tungsten Manager layer, which in turn controls the entire cluster. In this post we will explore the cctrl> service command and the power it provides to the admin.

In this post we discussed the tprovision command and why it is always best to use a Replica node, not the Primary node, as the source for provisioning another Replica node.

For 2023 and the future, Continuent has decided to focus more and more on important Climate related issues, naturally to the extent a software company can. To demonstrate this commitment, for the Holiday Season 2022 we have decided to donate 14 Mangrove trees for all Tungsten customer contacts as well as the internal Continuent team members, plus some friends and family members. Continuent has partnered with a Finnish company Treebuddy.Earth to get this done.

Tungsten Clustering contains many tools to monitor your cluster, and today we will look at a new one - the `tungsten_get_ports` command, included with Tungsten versions 6.1.20+ and 7.0.2+. This tool was created to help provide a clear view of running Tungsten processes and the associated listener ports.

This is a short blog answering the question: "I have a cron job running as a non-tungsten user, and that job needs access to the tungsten-owned files under /opt/continuent, but cannot access the files it needs - how do I give access to those files to my cron job?"

Need to do maintenance on a host? Learn how to suspend it gracefully.

Tungsten Clustering depends on a number of prerequisites and best practices to function optimally. In this blog post, we explore a critical, yet easily-overlooked step when installing a Tungsten Cluster node - configuring the available number of open files when using `systemd` control.