Testing elastic5 in beta cluster is not easy, we could use relforge to do early evaluations of cirrus+es5 on large indices.
|Resolved||debt||T151324 [epic] System level upgrade for cirrus / elasticsearch|
|Resolved||Deskana||T154501 [Epic, Q3 Goal] Upgrade search systems to Elasticsearch 5|
|Resolved||Gehel||T156150 Install ES 5.x to relforge100|
|Resolved||Deskana||T155578 Puppet changes required for elasticsearch 5.x upgrade|
|Resolved||Deskana||T158680 Upgrade codfw to ES 5.x|
|Resolved||Deskana||T159168 Add elasticsearch 5 .deb to reprepro experimental repository|
|Resolved||EBernhardson||T159203 Re-evaluate mapping for keywords|
After discussion with @dcausse, the following steps are needed to install ES5 on relforge:
- deploy gerrit change 333969
- remove indices using jieba plugin (curl localhost:9200/_settings | jq . | grep jieba)
- remove jieba, ltr and swift plugins and restart elasticsearch (on 2.x version), check that all indices still load correctly
- upgrade remaining plugins manually and upgrade elasticsearch (require a full cluster restart).
I forgot to mention this morning that upgrading to elastic5 will break sistersearch (the interwiki demo @Jdrewniak is working on).
It's unclear to me what are the priorities here.
I think the cirrussearch es5 branch is mostly ready to support simple searches so we should be able to migrate sistersearch the es5 branch.
I just wanted to point out that it may cause some disruption in the work Jan is doing.
@debt, @Jdrewniak thoughts?
Planning to upgrade the relforge servers beginning of next week. Expecting a short downtime for sistersearch, after which David or I will pull the es5 branches of CirrusSearch/Elastica to sistersearch to get things going again.