The MySQL Development Team is very happy to announce the second 8.0 Maintenance Release of InnoDB Cluster!
In addition to bug fixes, 8.0.13 brings some new exciting features:
Here are the highlights of this release!…
Tungsten Clustering is an extraordinarily flexible tool, with options at every layer of operation.
In this blog post, we will describe and discuss the two different methods for installing, updating and upgrading Tungsten Clustering software.
When first designing a deployment, the question of installation methodology is answered by inspecting the environment and reviewing the customer’s specific needs.
Staging Deployment Methodology
All for One and One for All
Staging deployments were the original method of installing
Tungsten Clustering, and relied upon command-line tools to
configure and install all cluster nodes at once from a central
location called the staging server.
This staging server (which could be one of the cluster nodes) requires SSH access to all …
[Read more]Your database cluster contains your most business-critical data and therefore proper performance under load is critical to business health. If response time is slow, customers (and staff) get frustrated and the business suffers a slow-down.
If the database layer is unable to keep up with demand, all applications can and will suffer slow performance as a result.
To prevent this situation, use load tests to determine the throughput as objectively as possible.
In the sample load.pl script below, increase load by
increasing the thread quantity.
You could also run this on a database with data in it without polluting the existing data since new test databases are created to match each node’s hostname for uniqueness.
Note: The examples in this blog post assume that a Connector is …
[Read more]In a previous post we went into detail about how to implement Tungsten-specific checks. In this post we will focus on the other standard Nagios checks that would help keep your cluster nodes healthy.
Your database cluster contains your most business-critical data. The slave nodes must be online, healthy and in sync with the master in order to be viable failover candidates.
This means keeping a close watch on the health of the databases nodes from many perspectives, from ensuring sufficient disk space to testing that replication traffic is flowing.
A robust monitoring setup is essential for cluster health and viability – if your replicator goes offline and you do not know about it, then that slave becomes effectively useless because it has stale data.
Nagios Checks The Power of Persistence
One …
[Read more]
The MySQL Replication was my first project as a Database
Administrator (DBA) and I have been working with Replication
technologies for last few years and I am indebted to contribute
my little part for development of this technology. MySQL supports
different replication topologies, having better understanding of
basic concepts will help you in building and managing various and
complex topologies. I am writing here, some of the key points to
taken care when you are building MySQL replication. I consider
this post as a starting point for building a high performance and
consistent MySQL servers. Let me start with below key
points Hardware. MySQL Server Version MySQL Server Configuration
Primary Key Storage Engine I will update this post with relevant
points, whenever I get time. I am trying to provide generic
concepts and it will be applicable to all version of MySQL,
however, some of the concepts are new and applicable to latest
versions …
MySQL Group Replication (GR) is a MySQL Server
plugin that enables you to create elastic, highly-available,
fault-tolerant replication topologies. Groups can operate in
a
single-primary mode with automatic primary election, where only
one server accepts updates at a time. Alternatively, groups can
be deployed in multi-primary mode, where all servers can accept
updates, even if they are issued concurrently.…
To resolve a critical regression, Percona announces the release of Percona XtraDB Cluster 5.7.23-31.31.2 on October 2, 2018 Binaries are available from the downloads section or from our software repositories.
This release resolves a critical regression in Galera’s wsrep library and supersedes 5.7.23-31.31
Percona XtraDB Cluster 5.7.23-31.31.2 is now the current release, based on the following:
Your database cluster contains your most business-critical data. The slave nodes must be online, healthy and in sync with the master in order to be viable failover candidates.
This means keeping a close watch on the health of the databases nodes from many perspectives, from ensuring sufficient disk space to testing that replication traffic is flowing.
A robust monitoring setup is essential for cluster health and viability – if your replicator goes offline and you do not know about it, then that slave becomes effectively useless because it has stale data.
Big Brother is Watching You! The Power of Nagios
Even while you sleep, your servers are busy, and you simply cannot keep watch all the time. Now, more than ever, with global deployments, it is literally impossible to watch everything all the time.
Enter Nagios, you best big brother ever. As a long-time player in the monitoring market, Nagios has both …
[Read more]This release has been superseded by 5.7.23-31.31.2 after a critical regression was found. Please update to the latest release.
Percona is glad to announce the release of Percona XtraDB Cluster 5.7.23-31.31 on September 26, 2018. Binaries are available from the downloads section or from our software repositories.
Percona XtraDB Cluster 5.7.23-31.31 is now the current release, based on the following:
[Read more]Continuent Clustering support true distributed multimaster clustering. In this topology, there are cross-site replicator services for each remote site. In a 3-site configuration, there are a total of 9 replication streams to manage.
Continuent Clustering also offers a graphical administration tool called the Tungsten Dashboard to help with your management burden. The GUI makes the deployment much easier to visualize and administer.
For our example, we will have a Composite Multimaster dataservice called global with three active, writable member clusters (one per site), east, west and north.
Dashboard Summary View
In the summary, collapsed view, the composite service and all member clusters are listed with associated information and controls. Note that the Type for the composite dataservice global is CompMM …
[Read more]
