This blog post explores the syncing options for an inconsistent MySQL slave of Galera cluster node using pt-table-sync
The post Fixing inconsistency on MySQL Slave of Galera Cluster first appeared on Change Is Inevitable.
This blog post explores the syncing options for an inconsistent MySQL slave of Galera cluster node using pt-table-sync
The post Fixing inconsistency on MySQL Slave of Galera Cluster first appeared on Change Is Inevitable.
This year, Percona introduced Community Voting for Percona Live submission. This is what you can read on the conference website:
In an effort to involve the larger community in the selection of speaking sessions for the 2016 Percona Live Data Performance Conference, we’ve implemented a community voting process. After a speaker submits a proposal we encourage sharing to the community and social
We're thrilled to announce VividCortex's new partnership with Percona -- the only company that delivers enterprise-class solutions for both MySQL and MongoDB across traditional and cloud-based platforms. As part of the partnership, Percona will resell VividCortex as a value-added monitoring solution, and Percona's own support technicians and managed service administrators will have VividCortex at their fingertips, to assist in serving and optimizing their customers’ applications.
Including VividCortex as part of Percona's services will provide enterprise users of Percona Server for MySQL and Percona Server for MongoDB with the safest, most streamlined, and precise method for monitoring high performance data systems. Percona customers who opt for VividCortex will enjoy improved visibility and greater insights into their database performance …
[Read more]Join us for our new webinar on Tuesday, December 22nd, which is also our last webinar in 2015!
Polyglot Persistence for the MongoDB, PostgreSQL & MySQL DBA
The introduction of DevOps in organisations has changed the development process, and perhaps introduced some challenges. Developers, in addition to their own preferred programming languages, also have their own preference for backend storage.The former is often referred to as polyglot languages and the latter as polyglot persistence.
Having multiple storage backends means your organization will become more agile on the development side and allows choice to the developers but it also imposes additional knowledge on the operations side. Extending your infrastructure from only MySQL, to deploying other storage backends like MongoDB and PostgreSQL, …
[Read more]In my previous post Amazon Aurora – Looking Deeper, I promised benchmark results on Amazon Aurora.
There are already some results available from Amazon itself: https://d0.awsstatic.com/product-marketing/Aurora/RDS_Aurora_Performance_Assessment_Benchmarking_v1-2.pdf.
There are also some from Marco Tusa: http://www.tusacentral.net/joomla/index.php/mysql-blogs/175-aws-aurora-benchmarking-blast-or-splash.html.
Amazon used quite a small …
[Read more]
In-memory performance and always-up drives our agenda. The
Percona Live Data Performance Conference is coming up with two
submitted sessions about Cluster.
If you want to learn from MySQL Cluster how to build high
performance solutions yourself then you should probably place a
vote on Developing for extreme performance. If you
want to know about the latest developments and how to build a
highly elastic real-time service based on MySQL Cluster then
Elastic real-time services with MySQL Cluster
is your session.
In the first technical session we will be taking a deep dive into
how to scale to …
Join Alexander Rubin, Principal Consultant, Percona as
he provides an overview of MySQL 5.7 features. Wednesday, December 9,
2015 10:00AM PST (GMT -08:00).
MySQL® 5.7 is a great release that has a lot to offer, especially in the areas of development and replication. It provides many new optimizer features for developers, a much more powerful GIS function, and a high performance JSON data type – allowing for a more powerful store for semi-structured data. It also features a dramatically improved Performance Schema and Parallel and Multi-Source replication – allowing you to scale much further than ever before.
Primary …
[Read more]
In the life of a professional MySQL DBA there comes a moment when
issues are no longer trivial enough to be diagnosed using simple
repros and built-in diagnostic commands. While trying to
understand complex problems, you may be forced (challenged?) to
look for answers at the lowest level, by analyzing the server's
source code.
If you're a seasoned database engineer who killed several
keyboards reporting MySQL bugs, you can stop reading now. If
you're just about to begin your journey into the source, you
could probably use all the help you can get so keep reading. In
this short article I'll describe the MySQL server tracing feature
I've been using as an aid during MySQL investigations. When
investigating issues at code level, one of the first questions
you will ask yourself is "where do I start?". Let's say you're
attempting to debug a SHOW CREATE …
Errant transactions are a major issue when using GTID replication. Although this isn’t something new, the drawbacks are more notorious with GTID than with regular replication.
The situation where errant transaction bites you is a common DBA
task: Failover. Now that tools like MHA have
support for GTID replication (starting from 0.56
version), this protocol is becoming more popular, and so
are the issues with errant transactions. Luckily, the fix is
as simple as …
Checksum is a standard practice among DBAs to verify the data consistency across replicated nodes. In this post we’re going to review the syncing options for an inconsistent MySQL slave of Galera cluster node.
Here we’re assuming a setup of regular replication to a MySQL
instance from one of the Galera cluster nodes.
In the usual MySQL replication setup, standard practice involves
the usage of the pt-table-checksum tool to identify the
discrepancies and usage of pt-table-sync to bring them in
sync. The checksum tool, pt-table-checksum, can run across
Galera cluster node to verify the data consistency and confirm if
the MySQL slave is consistent with a chosen primary node.
What happens if this Galera cluster’s regular MySQL slave sees
data inconsistency on it? Will pt-table-sync work there? The
answer to this depends…
pt-table-sync when used with –sync-to-master …