These come up when the job queue runs multiple updates out of order. They do not indicate any sort of problem and should not be logged to the CirrusSearchChangeFailed log
Description
Description
Event Timeline
Comment Actions
Just causes some log spam. We should fix it at some point... but it's not super high priority.
Comment Actions
A good first task is a self-contained, non-controversial task with a clear approach. It should be well-described with pointers to help a completely new contributor. Given the current short task description I'm removing the good first task tag. Please add details what exactly has to happen where and how for a new contributor, and then add back the good first task project tag. Would this need additional code in /includes/Job/ElasticaWrite.php or /includes/DataSender.php? Thanks a lot in advance.
Comment Actions
Closing out low/est priority tasks over 6 months old with no activity within last 6 months in order to clean out the backlog of tickets we will not be addressing in the near term. Please feel free to reopen if you think a ticket is important, but bare in mind that given current priorities and resourcing, it is unlikely for the Search team to pick up these tasks for the indefinite future. We hope that the requested changes have either been addressed by or made irrelevant by work the team has done or is doing -- e.g. upgrading Elasticsearch to a newer version will solve various ES-related problems -- or will be subsumed by future work in a more generalized way.
Comment Actions
Re-opening tasks and removing from team workboard per IRC feedback given yesterday and discussion with MPham.