[Toolserver-l] s3/s7 issues

[River Tarnell]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bryan Tong Minh:
> Would it be possible to revoke the drop command from the replication
> user to prevent this from happening in the future?

Yes.  I also considered modifying trainwreck (our replication tool) to 
ignore DROP DATABASE commands; perhaps we could do both.

It would be easier if these commands wouldn't find their way into the 
binlog in the first place, but mistakes happen.  Unfortunately there's 
no way to prevent every possible command that might break our database.

In the future I hope to have one MySQL instance per cluster, which would 
more closely mirror Wikimedia's configuration and hopefully make errors 
like this less common.

	- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)

iEYEARECAAYFAk01/BgACgkQIXd7fCuc5vIkHQCfYdoPQPCoV52VEDPt290CepZf
gD0AoJ5vmv/wXth2Pldw1n3DvVbOV01j
=Nj8x
-----END PGP SIGNATURE-----