AWS RDSGalera ClusterMariaDBMySQLMySQL-ArticlesTechnical6 comments Killer Blog for MySQL AdministratorsKedarDecember 9, 2024 This is by far the most killer MySQL blog that I wanted to write for really long as a part of a Killer DBA series. Time is hard to find,… View Post
Kedar
6 responses to “Killer Blog for MySQL Administrators”
Have you ever tried the SHUTDOWN command?
You can also have the possibility to execute the shutdown command using the mysql client.
How? Just typing “shutdown;”
It is useful when you have Galera or PXC, and you’re in doubt that whether that node was bootstrapped or not.
1.1 is pretty old.
yep. Shutdown works too! Thank you @marlonB and @rajeshSharma for noting this.
Thnk you for great topic and info
Great post!
For completeness, you may add another use case. One may test crash recovery by causing segmentation fault using SIGSEGV:
sudo kill -11 $(pidof mysqld)
In the error log this generates lines like
12:22:08 UTC – mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
…
Attempting backtrace…
…
Writing a core file …
Oh yes! Thanks for the tip Sasha.
Let me add similar trick…. invoke OoM killer similarly and MySQL being largest consumer almost always, this will kill mysqld.
sudo echo f > /proc/sysrq-trigger
Thanks