Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
MariaDB High Performance

You're reading from   MariaDB High Performance Familiarize yourself with the MariaDB system and build high-performance applications

Arrow left icon
Product type Paperback
Published in Sep 2014
Publisher
ISBN-13 9781783981601
Length 298 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Pierre Mavro Pierre Mavro
Author Profile Icon Pierre Mavro
Pierre Mavro
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

MariaDB High Performance
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Performance Introduction FREE CHAPTER 2. Performance Analysis 3. Performance Optimizations 4. MariaDB Replication 5. WAN Slave Architectures 6. Building a Dual Master Replication 7. MariaDB Multimaster Slaves 8. Galera Cluster – Multimaster Replication 9. Spider – Sharding Your Data 10. Monitoring 11. Backups Index

Use cases and troubleshooting


Use cases are really needed for novices and for those who do not practice these kind of solutions in production. That's why you'll see schema with explanations of what could happen in production. Now, let's discuss outages and how to resolve them.

SQL errors

In a replication mode, you can encounter errors if you do not respect what has been established. A common mistake is for the privileges to be configured on a slave node and not the master.

Here is a scenario with a database as an example:

  • Master: This is the server used as read/write

  • Slave1: This is the server used as read only

A junior database administrator connects to the slave server as someone asked for a new database and creates a database crap. The database is present on the slave node, but not the master. Two days later, another database administrator connects on the master node because he needs to perform an urgent insertion in that database. As he doesn't see it, he creates it now and performs the...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images