As people prepare for the "het deployment" of mw 1.18 you are going to see some interruptions of the dumps while I get these hosts ready for the switch. As a side effect of one of the configuration changes, the host running the "large-ish" wikis is temporarily not running any jobs. I should be starting those jobs again on Moday. The four "small wiki" processes should be ok.
When we get around to the actual deployment, I will likely stop all jobs til deployment is complete, as I cannot begin to guess what the output would look like if the codebase were switched out underneath the dumpers in the middle of a run.
Ariel
Ariel T. Glenn wrote:
As people prepare for the "het deployment" of mw 1.18 you are going to see some interruptions of the dumps while I get these hosts ready for the switch. As a side effect of one of the configuration changes, the host running the "large-ish" wikis is temporarily not running any jobs. I should be starting those jobs again on Moday. The four "small wiki" processes should be ok.
When we get around to the actual deployment, I will likely stop all jobs til deployment is complete, as I cannot begin to guess what the output would look like if the codebase were switched out underneath the dumpers in the middle of a run.
Ariel
PHP loads the files once, so given that all of them are likely to be loaded in the first revisions, it would be like running the whole dump with the old files. There could be some mismatch if several runners wwere on different versions, but that seems unlikely since the output is the same.
Στις 24-09-2011, ημέρα Σαβ, και ώρα 01:46 +0200, ο/η Platonides έγραψε:
Ariel T. Glenn wrote:
As people prepare for the "het deployment" of mw 1.18 you are going to see some interruptions of the dumps while I get these hosts ready for the switch. As a side effect of one of the configuration changes, the host running the "large-ish" wikis is temporarily not running any jobs. I should be starting those jobs again on Moday. The four "small wiki" processes should be ok.
When we get around to the actual deployment, I will likely stop all jobs til deployment is complete, as I cannot begin to guess what the output would look like if the codebase were switched out underneath the dumpers in the middle of a run.
Ariel
PHP loads the files once, so given that all of them are likely to be loaded in the first revisions, it would be like running the whole dump with the old files. There could be some mismatch if several runners wwere on different versions, but that seems unlikely since the output is the same.
Ah but not really. Because in the history phase of the dump, we respawn fetchText.php from a runner when we fail to retrieve revision text. This could be due to a revision where the text is permanently lost, a db server that's suddenly gotten unhappy, or something wrong with the child process' since we don't know and can't tell, we cover our bases and respawn our side of things. You would think that this doesn't happen very often but surprisingly there are a fair number of irretrievable revisions out there.
Ariel
xmldatadumps-l@lists.wikimedia.org