May 21, 2012

Post: Faster Point In Time Recovery with LVM2 Snaphots and Binary Logs

crashMySQL first, then unmount the logical volume holding the MySQL data. This way you don’t have to deactivate/activate the original logical volume to

Post: 10+ Ways to Crash or Overload MySQL

… trivial way to crash MySQL to the user with basic privileges and asking me what to do. My answer to them is – there is nothing new to it… :) Really – there are many ways to crash or otherwise made unavailable server with any MySQL version if you have access to it with normal privileges…

Post: MySQL for Hosting Providers - how do they manage ?

… little ways to really restrict how much resources single user can consume. I have written over a year ago about 10+ ways to crash or overload MySQL and since that people have come to me and suggested more ways to do the same. This is huge hole in MySQL

Comment: 10+ Ways to Crash or Overload MySQL

[...] the MySQL Performance Blog, Peter Zaitsev has another list: 10+ Ways to Crash or Overload MySQL. Writes Peter, “[There] are many ways to crash or otherwise made unavailable server with any [...]

Comment: 10+ Ways to Crash or Overload MySQL

[...] to really restrict how much resources single user can consume. I have written over a year ago about 10+ ways to crash or overload MySQL and since that people have come to me and suggested more ways to do the [...]

Comment: 10+ Ways to Crash or Overload MySQL

[...] – http://www.mysqlperformanceblog.com/2007/11/13/10-ways-to-crash-or-overload-mysql/ [...]

Comment: 10+ Ways to Crash or Overload MySQL

[...] 10+ Ways to Crash or Overload MySQL (0 visite) [...]

Comment: 10+ Ways to Crash or Overload MySQL

10+ Ways to Crash or Overload MySQL – в то время, как в…

Post: Fishing with dynamite, brought to you by the randgen and dbqp

10“]] Granted, these are insanely small values, but this is a test and we’re trying to do horrible things tomysql –basedir=/path/to/Percona-Server –suite=randgen_basic innodbDictSizeLimit_test This enabled us to reproduce the crash… reproduced crash. I will admit that there may be other ways to

Post: How quickly you should expect to see bugs fixed

10% of progress in 2hours qualifies as that). It is especially nasty as it is quite hard to predict. Both customers had MySQL crash… fixing it not MySQL/Sun but there are MySQL bugs not fixed for years too). Look for workarounds or ways to fix things yourself. In particular case workaround was rather easy – reducing Innodb buffer pool size to 4GB instead…