I want to take a moment to thank you for reading this blog. We are working very hard on cool tools for you to use with MySQL and we really enjoy spreading the news of these tools to you.  With this in mind I wanted to update you on something that is changing. We are moving to a new blog home at http://insidemysql.com/.  From this point on all new content will be posted on our new blog and we encourage each of you to update your bookmarks accordingly.  Our aggregator at http://planet.mysql.com/ has already been updated.

Don' t worry! The old posts will still be here so your old bookmarks will still work.  You can find our new Windows focused category at

…

Shots Architecture and how we handle extreme load spikes
I invite you to come out and join me in a talk about the above heading. I will describe many things and walk through the cases of what technology is used, where, why and how. The event information is located here. I'll also touch on, how cost is reduced, how we handle celebrity's load when they promote and what's next to make the system even more automatic and solid.
Thanks for sfmysql.org for all the work they do and for allowing me to give a talk.

IST Basics

State transfers in Galera remain a mystery to most people.  Incremental State transfers (as opposed to full State Snapshot transfers) are used under the following conditions:

• The Joiner node reports Galera a valid Galera GTID to the cluster
• The Donor node selected contains all the transactions the Joiner needs to catch up to the rest of the cluster in its Gcache
• The Donor node can establish a TCP connection to the Joiner on port 4568 (by default)

IST states

Galera has many internal node states related to Joiner nodes.  They currently are:

1. Joining
2. Joining: preparing for State Transfer
3. Joining: requested State Transfer
4. Joining: receiving State Transfer
5. Joining: State …

Why Multi source replication is required?

MySQL has limitation of not allowing to replicate multiple DB’s from different master host on a single slave. MySQL replication had a limitation, fixed with this new release, that said that one slave could have only one master. That is a limiting factor when we are designing our replication environment. There were some “hacks” to make it work, but now there is an official way.

What is multisource replication?
MySQL Multi-Source Replication enables a replication slave to receive transactions from multiple sources simultaneously. Multi-source replication can be used to back up multiple servers to a single server, to merge table shards, and consolidate data from multiple servers to a single server. Multi-source replication does not implement any conflict detection or resolution when applying the transactions, and those tasks are left to the …

Hi,

I think most of the DBAs experience this error in their weekly, monthly todo list. Each one follows different approach, I would like to share some tips here:

1. You should first execute “Show Slave Status;” and check the output, analyze it. Whether SQL thread has stopped or I/O thread has stopped and check respective error , It should be either SQL error or I/O error, based on that take next step.

I/O thread has stopped:

1. Check that you can reach the master host from slave hostby using ping or traceroute/tracert to reach the host.
2. Connect to Master host and check whether “Replication thread” is connected.
3. There are multiple thread state involved, you need to take action based on thread state –  …

Migrating your database to a new datacenter can be a high-risk and time-consuming process. A database contains state, and can be much harder to migrate as compared to web servers, queues or cache servers. 

In this blog post, we will give you some tips on how to migrate your data from one service provider to another. The process is somewhat similar to our previous post on how to upgrade MySQL, but there are a couple of important differences. 
 
This is the seventh installment in the ‘Become a MySQL DBA’ blog series. Our previous posts in the DBA series include Database Upgrades, …

UPDATE: Almost solved! See at the end.

A clean installation of a database server is one where everything goes according to the expectations. It used to be easy: you only had to do what the manual says, and, presto! you would see your database server installed and ready to use. If something went wrong, you got one or more error messages that informed you of what needs to be fixed.

Sometimes, rarely, it happened that you got also a warning message, telling you that while the installation was successful, you could improve it by fine tuning this and that. No big deal.

Gone are those times. A clean installation nowadays is a much harder exercise, if not impossible. Let’s give it a try using MySQL 5.7.7.



Attempt #1 using mysql_install_db
The first error you could do when using a new version of MySQL is assuming that basic operations are …

[…] PlanetMySQL Voting: Vote UP / Vote DOWN Full article:NDB 7.4 & SYS schema: When getting locks, detecting the guilty SQL & o.s.pid. […]

VividCortex is sponsoring and exhibiting at Velcoity EU in Amsterdam October 28 - 30th. Stop by our booth to get a free product demo and see how we can revolutionize your database monitoring.

Baron Schwartz will also be speaking on Probabilistically Sampling A Stream Of Events With A Sketch.

Click here for more details and registration.

VividCortex is sponsoring and exhibiting at Velcoity EU in Amsterdam October 28 - 30th. Stop by our booth to get a free product demo and see how we can revolutionize your database monitoring.

Baron Schwartz will also be speaking on Probabilistically Sampling A Stream Of Events With A Sketch.

Click here for more details and registration.