September 22, 2014

MySQL High Availability With Percona XtraDB Cluster (Percona MySQL Training)

Percona XtraDB Cluster 5.6I’ve had the opportunity to train lots of people on Percona XtraDB Cluster (PXC) over the last few years the product has existed.  This has taken the form of phone calls, emails, blog posts, webinars, and consulting engagements. This doesn’t count all the time I’ve spent grilling Codership on how things actually work.  But it has culminated in the PXC tutorial I have given annually at Percona Live MySQL Conference and Expo in Santa Clara, California for the last two years.  Baron even attended this year and had this say:

“Jay Janssen’s tutorial on Percona XtraDB Cluster was impressive. I can’t imagine how much time he must have spent preparing for that.”

(Baron: Thanks for this compliment, BTW)  The answer is: I haven’t kept track, but I’ve delivered it 3 times at conferences and it gets better each time.  I started working on it during the summer of 2012 for Percona Live NYC that year and have put in countless hours since making it better.  This year, despite my voice problems, I was really happy with how it came out.

We’ve had lots of requests for repeats of this tutorial and with more detail.  As such, I’ll be doing a 2-day training about MySQL HA with Percona XtraDB Cluster in sunny San Jose, California on July 16th -17th 2014.  This Percona MySQL Training session is appropriately titled, “MySQL High Availability With Percona XtraDB Cluster” and you can get more information and also register here.

This course will include an overview of how Percona XtraDB Cluster fits into the MySQL High Availability world, followed by a deep-dive into PXC.  All the content of the tutorial will be covered, but it will be spread out with more details on all the components and important bits of using PXC and Galera.

If you’re unfamiliar with my tutorial — it is intensively hands-on.  This will not be 2 days of lecture: You’ll be setting up and experimenting with a real cluster on the fly during the class. Expect plenty of command-line work and to leave with a much better sense of how to truly operate and use a Percona XtraDB Cluster.

Once again, you can check out the details on our website and register NOW to attend right here.

About Jay Janssen

Jay joined Percona in 2011 after 7 years at Yahoo working in a variety of fields including High Availability architectures, MySQL training, tool building, global server load balancing, multi-datacenter environments, operationalization, and monitoring. He holds a B.S. of Computer Science from Rochester Institute of Technology.

Comments

  1. Phil Stracchino says:

    Jay, I attended your XtraDB Cluster training class in July, and I have come up with a few questions.

    First, I have occasionally run into problems in which a joining node will try to connect to *itself*, and fail, if its address is the first in wsrep_cluster_address. Since this variable is fully maintained in memory by the cluster once the node joins, I have taken to omitting each node’s own address from wsrep_cluster_address. Do you see any problem with this practice, or any reason why it should not be done, other than convenience in setting up the config file?

    Secondly, since XtraDB Cluster already uses its own internal transaction UUIDs, it seems to me that using MySQL 5.6 GTIDs within XtraDB Cluster would be redundant. What is your viewpoint on this?

    And third, do you see any problem with using innodb_buffer_pool_dump_at_shutdown and innodb_buffer_pool_load_at_startup with XtraDB Cluster? Do you have an opinion on whether it should or should not be used?

  2. >>First, I have occasionally run into problems in which a joining node will try to connect to *itself*, and fail, if its address is the first in wsrep_cluster_address. Since this variable is fully maintained in memory by the cluster once the node joins, I have taken to omitting each node’s own address from wsrep_cluster_address. Do you see any problem with this practice, or any reason why it should not be done, other than convenience in setting up the config file?

    That’s a bug and it should be reported as such here: https://bugs.launchpad.net/percona-xtradb-cluster/+filebug
    It’s likely something special with your config. I don’t like having a special config per host just because it complicates things operationally.

    >> Secondly, since XtraDB Cluster already uses its own internal transaction UUIDs, it seems to me that using MySQL 5.6 GTIDs within XtraDB Cluster would be redundant. What is your viewpoint on this?

    If you are using async replication with PXC, then GTIDs for that may be of some value for you: http://www.percona.com/blog/2014/02/14/changing-async-slave-pxc-cluster-new-master-using-5-6-gtid/

    >> And third, do you see any problem with using innodb_buffer_pool_dump_at_shutdown and innodb_buffer_pool_load_at_startup with XtraDB Cluster? Do you have an opinion on whether it should or should not be used?

    No, it should generally be fine.

  3. Phil Stracchino says:

    Thanks for the prompt response, Jay. :)

Speak Your Mind

*