-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
After the s3/s7 split at Wikimedia, which moved several databases from s3 to the new s7 cluster, we retained both databases on the same (s3) server, which is our usual policy in such cases.
Unfortunately, over the last couple of days Wikimedia executed several DROP DATABASE statements on their s7 server, for the old s3 databases. These statements were replicated to our s3/s7 server and dropped the live databases on our server. As a result:
* Several s3 databases (all of which start with 'a') are no longer available * s3 replication is halted due to the missing databases * s7 replication is halted to prevent further destruction of data.
The only way to resolve this issue is to re-import the data from Wikimedia's databases, which will take a few days at least.
- river.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
River Tarnell:
- Several s3 databases (all of which start with 'a') are no longer available
- s3 replication is halted due to the missing databases
- s7 replication is halted to prevent further destruction of data.
The only way to resolve this issue is to re-import the data from Wikimedia's databases, which will take a few days at least.
This should be fixed now. s3 is fine, while s7 is replicating but ~2.5 days behind. It should catch up within the next day or so. Currently only hyacinth is serving s3, s4, s6 and s7; once s7 has caught up, we will copy its data to cassia and re-add the secondary server.
- river.
toolserver-announce@lists.wikimedia.org