Last modified: 2014-06-19 23:08:40 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T68858, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 66858 - CirrusSearch: Never try to update the same page twice in the same update run
CirrusSearch: Never try to update the same page twice in the same update run
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
CirrusSearch (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-19 20:25 UTC by Nik Everett
Modified: 2014-06-19 23:08 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Nik Everett 2014-06-19 20:25:48 UTC
See this:
2014-06-19 20:03:57 mw1007 enwiki: Update for doc ids: 38124800,38124800; error message was: Error in one or more bulk request actions:

update: /enwiki_content_1401733677/page/38124800 caused VersionConflictEngineException[[enwiki_content_1401733677][5] [page][38124800]: version conflict, current [177], provided [176]]


Why in the world are we trying to update the same page twice? Of course it isn't going to work!  Elasticsearch will update the page once and then quickly try again and get a version conflict with the update it just did!
Comment 1 Gerrit Notification Bot 2014-06-19 21:41:34 UTC
Change 140825 had a related patch set uploaded by Chad:
Prevent duplicate updates

https://gerrit.wikimedia.org/r/140825
Comment 2 Gerrit Notification Bot 2014-06-19 23:06:43 UTC
Change 140825 merged by jenkins-bot:
Prevent duplicate updates

https://gerrit.wikimedia.org/r/140825

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links