The MySQL Development Team is happy to announce a new 8.0 Maintenance Release of MySQL Shell AdminAPI – 8.0.21!
As always, we have listened to the growing community of users and introduced a very useful feature for any production deployment of MySQL InnoDB Cluster or ReplicaSet.…
Facebook Twitter LinkedIn
The MySQL Development Team is happy to announce a new 8.0 Maintenance Release of MySQL Shell AdminAPI – 8.0.20!
Following the previous exciting release, on which InnoDB ReplicaSet was introduced, we focused on improving the management of ReplicaSets but also, most importantly, InnoDB cluster.…
Facebook Twitter LinkedIn
Overview The Skinny
In this blog post we explore various options for tuning MySQL traffic routing in the Tungsten Connector for better control of the distribution.
A Tungsten Cluster relies upon the Tungsten Connector to route client requests to the master node or optionally to the slaves. The Connector makes decisions about where to route requests based on a number of factors.
This blog post will focus on the Load Balancer algorithms available via configuration that allow you to adjust the routing behavior of the Connector, along with ways to debug the Connector Load Balancer’s routing decisions.
The Question Recently, a customer asked us:
How do I know which load balancer algorithm is in use by the Connector? And how do we enable debug logging for the Connector load balancer?
…[Read more]The MySQL Development Team is thrilled to announce a new 8.0 Maintenance Release of MySQL Shell AdminAPI – 8.0.19!
This release sets the bar higher, by introducing a new integrated solution based on a very well known Replication technology – MySQL InnoDB ReplicaSet!…
Facebook Twitter LinkedIn
Following MySQL InnoDB Cluster as our first, fully integrated MySQL High Availability solution based on Group Replication, MySQL Shell 8.0.19 includes MySQL InnoDB ReplicaSet which delivers another complete solution, this time based on MySQL Replication.
The basic idea for InnoDB ReplicaSet is to do the same for classic MySQL Replication as InnoDB Cluster did for Group Replication.…
Facebook Twitter LinkedIn
Its not the new term for DBAs. MySQL has an awesome parameter
innodb-file-per-tables allows MySQL to create
separate files for each tables. This helped a lot to manage the
disk space in more efficient way. But when we perform a large
batch job for delete or update the data in MySQL tables, you may
face this fragmentation issue. Comparing with SQL server, MySQL’s
fragmentation is not high. I had a similar situation where my
Disk space was consuming 80% and when I check the huge files in
OS, one table’s idb file consumed 300GB+. I know it
has some wasted blocks(but not actually wasted, MySQL will use
this space, it’ll not return this to OS) Then I checked the
information schema to find out the data size and its
index size. It was 27GB only. Then I realize, we did a batch
operation to delete many billions of records in that table.
Thanks to Rolando - MySQL DBA:
When I searched the similar …
[Read more]The MySQL Development Team is very happy to announce a new 8.0 Maintenance Release of InnoDB Cluster – 8.0.18.
In addition to major quality improvements, 8.0.18 brings some very useful features!
This blog post will only cover InnoDB cluster’s frontend and control panel – MySQL Shell and its AdminAPI – Stay tuned for other blog posts covering MySQL Router and Group Replication!…
Facebook Twitter LinkedIn
Overview The Skinny
In this blog post we explore various options for performance tuning MySQL server for better slave replication performance.
A Tungsten Cluster relies upon the Tungsten Replicator to move events from the master node to the slaves. Once the event has been transferred to the slave as THL on disk, the slave applier will then attempt to write it to the database. The Replicator can only apply events as fast as MySQL allows. If the MySQL server is somehow slow or blocking, then the Replicator will be as well.
A properly-tuned database server in addition to infrastructure and SysAdmin best practices will go quite a long way towards high-performance slave apply.
The Question Recently, a customer asked us:
During one of our load tests, we had a peak of 60k writes/min, averaging …
[Read more]Overview The Skinny
Part of the power of Tungsten Clustering for MySQL / MariaDB is the ability to perform true zero-downtime maintenance, allowing client applications full access to the database layer, while taking out individual nodes for maintenance and upgrades. In this blog post we cover various types of maintenance scenarios, the best practices associated with each type of action, and the key steps to ensure the highest availability.
Important Questions Understand the Environment as a Whole First
There are a number of questions to ask when planning cluster maintenance that are critical to understand before starting.
For example:
The Question Recently, a customer asked us:
How would we manually move the relay role from a failing node to a slave in a Composite Tungsten Cluster passive site?
The Answer The Long and the Short of It
There are two ways to handle this procedure manually when the
usual switch command fails to work as expected. One
is short and reasonably automated, and the other is much more
detailed and manual.
Of course, the usual procedure is to just issue the
switch command in the passive cluster:
use west set policy maintenance switch set policy automatic
The below article describes what to do when the
switch command does not move the relay role to
another node.
SHORT
Below is the list of cctrl commands that would be run for the basic, short version, which (aside from handling policy changes) is really only three …
[Read more]
