MariaDB

In this blog, we cover tprovision. tprovision is a complete rewrite of the provisioning tool “tungsten_provision_slave,” included with Tungsten Cluster. It is streamlined and allows easy provisioning of replica databases.

Tungsten Clustering is a powerful tool with many moving parts, including the Tungsten Connectors which may be installed on any application server. During a troubleshooting event, it is helpful to understand what to look for and where, in addition to understanding how the logs work together to provide a clear picture of the situation. In Tungsten version 7, we introduced a number of features designed to make troubleshooting easier, and this blog will cover some of that too.

Tungsten Clustering allows for many types of maintenance to happen with no downtime at all. This blog post will explore how to upgrade the actual MySQL Server on all cluster nodes with zero downtime.

This blog post will walk you through configuring HA Proxy for the Tungsten Dashboard, along with the new command `tpm generate-haproxy-for-api` which helps automate the process by translating existing INI files into haproxy.cfg config file format. The Tungsten Dashboard is a browser-based GUI, designed to make using a Tungsten Cluster as easy as possible.

Transaction History Log (THL) files are the core of Tungsten Replication, containing the actual MySQL write events that are replicated to the replicas. These files can take up considerable amounts of disk space, making them of interest for housekeeping operations to limit the consumption and ultimately, the cost. This blog post will walk you through THL management, along with the new command `tpm purge-thl` which helps automate the process when THL needs to be removed prior to the automatic rotation window.

Thinking transparent reconnects of applications is the grail of HA? It is! But Active/Active setups make them risky.

We are pleased to announce that Tungsten Clustering and Tungsten Replicator GA versions 7.0.1 are now available. This new minor release includes 52 new features and improvements, including two critical bug fixes. Read this blog to learn about the new v7.0.1 release!

Performance tuning any system provides more speed for the same hardware spend, gives the end-user a better, faster experience and typically reduces the stress on staff all around. Security tuning locks down critical data to prevent unauthorized access. Today we will explore both the security and performance enhancements available for the Tungsten Replicator THL sub-system as of version 7.x.

Sometimes you really, really want to know what a MySQL client is asking of the MySQL server. As of Tungsten Clustering v7.0.0, you may now enable Connector Audit Logging, which captures data transferred between client applications and MySQL servers to a file, database or socket. This blog post will walk you through the feature and how to enable, configure and disable Tungsten Connector Audit Logging.

Deploying Composite Active/Active clusters gives end-users the best experience no matter where they are located. Tungsten Cluster makes this possible with the deployment of MySQL clusters at geo-scale, allowing the enterprise to host clusters close to the users. How can we avoid write-conflicts with asynchronous replication and multiple primary databases?

In this post we will explore a new command in v7.0.1, tpm report. The purpose of tpm report is to provide easy access to all of the settings that pertain to a specific topic. Since Security is a high priority at Continuent, the current default (and only) topic is the Security stance. The tpm report command will evolve and grow over time. This first version is Continuent’s way of providing as much transparency about Tungsten Cluster Security as possible.

We are pleased to announce that Tungsten Clustering and Tungsten Replicator GA version 6.1.17 are now available. Tungsten allows enterprises running business-critical MySQL database applications to cost-effectively achieve continuous global operations with commercial-grade high availability (HA), geographically redundant disaster recovery (DR) and geographically distributed active/active.