New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
three archiving fixes #16548
three archiving fixes #16548
Conversation
…xisting done archive is useable.
👍 |
…chiveSelector::getArchiveIdAndVisits
@tsteur found another (potential) issue fixed in a075a9b code's a bit confusing, but I don't think it can be made much simpler (we need to get the latest idarchives for each requested plugin, then ignore older ones, and ignore the all plugins archive if individual plugin archives are found). this should avoid some odd edge cases. will merge if the build passes, but could use a review after the fact. |
@tsteur here's an example of the query, btw:
the explain for it is:
|
Changes:
unset status on failed archiving jobs so they will be picked up again in the next core:archive run
make sure ArchiveSelector::getArchiveIds behaves consistently with ArchiveSelector::getArchiveIdAndVisits
make sure the 'done' all plugins archives aren't used w/ pluginOnly=1, otherwise we will see the 'done' archive and assume we can use it. pluginOnly=1 is used when an invalidation for a specific plugin/report is added (ie, w/ reArchiveReport). so if it's set, and we find a usable archive, we force archiving again.
NOTE: this should only happen in core:archive when we see an invalidation w/ the plugin column set. I don't think this can currently happen outside of ArchiveInvalidator::reArchiveReport().
FYI @tsteur