Tomasz Finc wrote:
Is the re-compression in an automated enough state to
do the next chunks
on its own? Curious to see if you have to do all the shepherding for this.
There's still some need for human involvement.
Also, there are some potential traps even for humans. There are
continuing issues from bug 20757 and bug 22624, and as we recompress
more recent clusters, we will run into bugs caused by extensions that
interact directly with external storage, such as CodeReview,
FlaggedRevs and AbuseFilter.
Any extension that follows the example from CodeReview and implements
its own private text table will be a serious problem for RCT and will
cause bit rot and data loss.
I added some protections for known bugs in trackBlobs.php in trunk. If
you run the trunk version of trackBlobs.php on Wikimedia at the
moment, it will just exit with an error (for good reason).
-- Tim Starling