-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hi,
the user database server (zedler) has run out of space on the MySQL filesystem; however, there is still 250GB free in the InnoDB table space. to reclaim this free space, we need to dump the reload the database. the database will be inaccessible while this is in progress.
based on the time taken to run nightly backups, the dump should take about 5 hours. however, i will run it in parallel to improve performance. it will take a bit longer to reload it afterwards.
after the reload, i will not restore the commonswiki replica that was previously on the sql server. the correct way to join user databases to commons is to create them on the sql-s4 server.
- river.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
we successfully dumped the databases, but after a reboot, the SCSI card attaching the server to its external disk array malfunctioned (it's likely this happened previously and wasn't noticed until a reboot).
i am currently looking for a temporary solution to bring user databases back online until the server can be repaired or replaced.
- river.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
i have started a MySQL instance on another server which will temporarily serve as 'sql', and have started importing the databases. this will probably take a while.
- river.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
today we replaced the SCSI card in zedler (sql); during the maintenance, yarrow's disk array unexpectedly rebooted which caused MySQL to crash. it is currently running database recovery and will be available again shortly.
at some point in the next week we will move the user databases from the temporary server back to zedler (by copying the data files directly, which will be much faster).
- river.
Hi,
I have start last week one little perl project with database access. I use in mysql my very old database u_sk_yarrow.
I don't know where the name yarrow come from, but I see at this graphic http://de.wikipedia.org/wiki/Datei:Toolserver-cluster.svg that it is one of the sql-server.
Is this name ok or should I rename the database in u_sk_something_p? So that it is public. I don't see a other database with "yarrow" in the name.
After the downtime of mysql my database is empty. No tables. Should I wait for the recover or should I recreate the tables by myself?
Maybe this are easy question, but this is my first little project with database access at the toolserver.
Thanks, Stefan (sk)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Stefan Kühn:
I don't know where the name yarrow come from
a long time ago, we migrated the user database server (sql) from yarrow to zedler. for users who already had data in both servers, we imported the databases from yarrow to the new server with a _yarrow suffix.
Is this name ok or should I rename the database in u_sk_something_p? So that it is public.
only you can answer this. do you want the data to be public? in that case you will need to rename it. otherwise, there is no need to do so.
I don't see a other database with "yarrow" in the name.
there are many, but you can't see them, because they aren't public.
After the downtime of mysql my database is empty. No tables.
at the time you wrote this mail, the maintenance was still in progress and 'sql' was still down. you should not even have been able to connect to it, let alone see any databases there.
the maintenance is now over and all databases should be there.
- river.
Many thanks for this infos.
The project is now running. Thanks for your work.
Stefan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
the import is now finished and user databases are accessible again.
- river.
toolserver-l@lists.wikimedia.org