Last modified: 2014-05-11 14:24:07 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 T65418, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63418 - CirrusSearch: Use index replica settings when creating the version tracking index
CirrusSearch: Use index replica settings when creating the version tracking i...
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-04-02 14:30 UTC by Nik Everett
Modified: 2014-05-11 14:24 UTC (History)
4 users (show)

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


Attachments

Description Nik Everett 2014-04-02 14:30:31 UTC
If folks have only a single node they aren't likely to be able to use the default number of replicas.
Comment 1 Gerrit Notification Bot 2014-04-02 15:25:02 UTC
Change 123243 had a related patch set uploaded by Chad:
Set mw_cirrus_versions to have no replicas

https://gerrit.wikimedia.org/r/123243
Comment 2 Gerrit Notification Bot 2014-04-02 15:31:21 UTC
Change 123243 merged by jenkins-bot:
Set mw_cirrus_versions to have no replicas

https://gerrit.wikimedia.org/r/123243
Comment 3 Chad H. 2014-04-02 20:10:11 UTC
You'll need to manually lower/raise the existing replica settings (or blow away mw_cirrus_versions and rebuild it). The default's no replicas now so should be fine for all installs going forward though.
Comment 4 keyler 2014-04-11 14:56:00 UTC
Great, I will try it in the next days... Thank you!
Comment 5 keyler 2014-05-11 14:24:07 UTC
I now just deleted the "mw_cirrus_versions" and everything seems to work. And ElasticSearch is "green" again ;-)
Thank you guys...

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


Navigation
Links