Continuent provides multiple methods out of the box to monitor the cluster health. It integrates with monitoring and alerting tools like Nagios/NRPE, Zabbix, and Pagerduty. This blog post shows you the thinking behind each included Tungsten Cluster monitoring tool, and when to use which tool.
This blog is about troubleshooting failed DDL across all Replicas in a composite active/active (CAA) Tungsten Cluster. The issue was resolved by setting a more permissive SQL_MODE, then locating and cleaning the bad data with proper NULLs before re-issuing the ALTER TABLE.
SmartScale is a special mode of the Tungsten Connector (aka Tungsten Proxy), which allows read requests to be intelligently routed to either a replica or the primary to ensure that the data returned is not stale. This feature is available when the Connector is running in the application-layer Proxy mode. Learn more about the behavior of SmartScale in this blog.
Application performance and MySQL database responsiveness is always high priority for highly-available, business-critical use cases. That’s why Tungsten Clustering offers features and options to tune for maximum performance, such as Parallel Apply. When does Parallel Apply work best? What are the limitations? To find out, read this blog from MySQL industry vet, Eric M. Stone, the COO of Continuent!
Upgrades are a normal, expected part of all software lifecycles, and Tungsten is no exception. Keep your software up-to-date to ensure compatibility, supportability and the lowest risk possible to your operation.
The new role of recovery (RPO and RTO) in a continuous, highly available MySQL environment?
In this blog post, we explore how the two new Tungsten Replicator roles allow for THL transfer when not actively extracting or applying events. This new behavior provides for better control and performance under a variety of conditions.
In this short blog post, we examine the impact that setting the Tungsten cluster policy to Maintenance has on the cluster behavior, and specifically the impact on the Tungsten Connector.
Performing MySQL schema changes often requires downtime for applications. In this blog, we cover two ways we can perform MySQL schema changes without risking downtime or other MySQL data problems. In this real-life customer example, we perform a schema change to modify the column data type from varchar(20) to varchar(50) on approx. 35 tables from 3GB to 10GB in size. Two of the tables are partitioned, and one of them is about 100GB combining all partitions for that table.
Learn how and where the Connector communicates, and about the different SSL configurations possible.
This blog discusses some best practices for using multiple filesystems on MySQL database servers and how to achieve the best performance with them, while avoiding some of the possible pitfalls.
