The XML database dumps are missing all through May, apparently because of a memory leak that is being worked on, as described here, https://phabricator.wikimedia.org/T98585
However, that information doesn't reach the person who wants to download a fresh dump and looks here, http://dumps.wikimedia.org/backup-index.html
I think it should be possible to make a regular schedule for when these dumps should be produced, e.g. once each month or once every second month, and treat any delay as a bug. The process to produce them has been halted by errors many times in the past, and even when it runs as intended the interval is unpredictable. Now when there is a bug, all dumps are halted, i.e. much delayed. For a user of the dumps, this is extremely frustrating. With proper release management, it should be possible to run the old version of the process until the new version has been tested, first on some smaller wikis, and gradually on the larger ones.
hear hear Gerard
On 29 May 2015 at 01:52, Lars Aronsson [email protected] wrote:
The XML database dumps are missing all through May, apparently because of a memory leak that is being worked on, as described here, https://phabricator.wikimedia.org/T98585
However, that information doesn't reach the person who wants to download a fresh dump and looks here, http://dumps.wikimedia.org/backup-index.html
I think it should be possible to make a regular schedule for when these dumps should be produced, e.g. once each month or once every second month, and treat any delay as a bug. The process to produce them has been halted by errors many times in the past, and even when it runs as intended the interval is unpredictable. Now when there is a bug, all dumps are halted, i.e. much delayed. For a user of the dumps, this is extremely frustrating. With proper release management, it should be possible to run the old version of the process until the new version has been tested, first on some smaller wikis, and gradually on the larger ones.
-- Lars Aronsson ([email protected]) Aronsson Datateknik - http://aronsson.se
Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 05/28/2015 07:52 PM, Lars Aronsson wrote:
With proper release management, it should be possible to run the old version of the process until the new version has been tested, first on some smaller wikis, and gradually on the larger ones.
I understand your frustration; however release management was not the issue in this case. According to Ariel Glenn on the task (https://phabricator.wikimedia.org/T98585#1284441), "It's not a new leak, it's just that the largest single stubs file in our dumps runs is now produced by wikidata!".
I.E. it was caused by changes to the input data (i.e. our projects), not by changes to the code.
Matt Flaschen
Hello! I've noticed that no enwiki dump seems to have been generated so far this month. Is this by design, or has there been some sort of dump failure? Does anyone know when the next enwiki dump might happen?
Kind regards.
Neil Harris
On Sun, Jan 10, 2016 at 9:55 PM, Neil Harris [email protected] wrote:
Hello! I've noticed that no enwiki dump seems to have been generated so far this month. Is this by design, or has there been some sort of dump failure? Does anyone know when the next enwiki dump might happen?
I would also be interested.
On Sun, Jan 10, 2016 at 4:05 PM, Bernardo Sulzbach < [email protected]> wrote:
On Sun, Jan 10, 2016 at 9:55 PM, Neil Harris [email protected] wrote:
Hello! I've noticed that no enwiki dump seems to have been generated so
far
this month. Is this by design, or has there been some sort of dump
failure?
Does anyone know when the next enwiki dump might happen?
I would also be interested.
-- Bernardo Sulzbach
Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
CCing the Xmldatadumps mailing list https://lists.wikimedia.org/mailman/listinfo/xmldatadumps-l, where someone has already posted https://lists.wikimedia.org/pipermail/xmldatadumps-l/2016-January/001214.html about what might be the same issue.
On Mon, Jan 11, 2016 at 3:22 AM, Tilman Bayer [email protected] wrote:
CCing the Xmldatadumps mailing list https://lists.wikimedia.org/mailman/listinfo/xmldatadumps-l, where someone has already posted https://lists.wikimedia.org/pipermail/xmldatadumps-l/2016-January/001214.html about what might be the same issue.
For some reason, I did not subscribe to that list. Thanks for pointing it out.
That would be me; I need to push some changes through for this month but I was either travelling or dev summit/allstaff. I'm pretty jetlagged but I'll likely be doing that tonight, given I woke up at 5 pm :-D
A.
On Mon, Jan 11, 2016 at 4:20 PM, Bernardo Sulzbach < [email protected]> wrote:
On Mon, Jan 11, 2016 at 3:22 AM, Tilman Bayer [email protected] wrote:
CCing the Xmldatadumps mailing list https://lists.wikimedia.org/mailman/listinfo/xmldatadumps-l, where someone has already posted <
about what might be the same issue.
For some reason, I did not subscribe to that list. Thanks for pointing it out.
-- Bernardo Sulzbach
Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l