Percona Live London MySQL Conference, November 11-12 2013
Codership's Galera Cluster team will be present this year as Platinum sponsor of the event, and we're excited for the opportunity to showcase the latest developments of Galera Cluster to Europe's MySQL community in London. We will have two talks at the event, as described below and will also be present in the exhibition hall with a Galera Cluster booth. Make sure to say hello and meet our experts at the booth to discuss all things related to Galera Cluster & beyond.
Talk 1: Galera Cluster 3.0 – new features
12 November 11:00am - 11:50am @ Sentosa 5-8, by Seppo Jaakola, CEO, Codership
This session presents Galera Cluster synchronous multi-master feature and functionality and the new features of Galera Cluster 3.0, including MySQL 5.6 compatibility and how Galera makes the best match with 5.6 features, especially for multi-master WAN or cloud deployments for business critical applications.
- Galera Cluster 3.0, synchronous multi-master feature and functionality overview
- How Galera and MySQL global transaction identifiers (GTIDs) play together in the hybrid Galera/MySQL replication topologies
- Improved quorum calculation, helping with multiple data center deployments
- Optimized WAN replication, boosting geoclustering deployments
Talk 2: How to understand Galera Replication
12 November 5:00pm - 5:50pm @ Sentosa 5-8, by Alexey Yurchenko, Solutions Architect, Codership
Galera was conceived from the ground up to be the simplest replication solution possible. And it really is very simple. But it is also very different from traditional replication approaches, and thus may be non-trivial to grasp at first sight.
If you looked at Galera replication for MySQL (Percona XtraDB Cluster, MariaDB Galera Cluster), even tried it, and asked one of the following questions, it means you are thinking in terms of old-school MySQL replication or some other replication technology other than Galera:
- What happens when the primary node dies?
- Does Galera use 2 phase commit?
- What happens when a transaction is committed on the master but fails on the slave?
- When all nodes have certified the transaction, do they then "approve" the commit back to the master?
- How can I setup read-only slaves?
- How do I promote another node to master? How does failover happen?
- How do I change the number of nodes in the cluster?
- If a node is disconnected from the cluster, how can I prevent my application from writing to it to avoid inconsistent slave issues?
If you are trying to ask the above questions about Galera, then you should attend this talk - it will help you to make sense out of it all.
Register now! We look forward to seeing you in London!