798155 - Upgrade ES on ci.mozilla.org from 0.17.4 to latest 0.20.x

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task, P5)

Description

[Brandon Burton [:solarce]]

Upgrade ES on ci.mozilla.org from 0.17.4 to latest 0.19.x for performance and stability reasons

I will work with :phrawzty on this

Comment 1

[Daniel Maher [:phrawzty]]

Are we sure that Jenkins supports ES 0.19.x ?  I ask because there are API changes between the two versions, so that's a concern.  If we're confident on that point, then the next question is whether we want to keep the indices or not - if not, then it's super-easy, since we just remove the old ver and replace it with a new one.  If we want to preserve the data, then we can think more about that strategy, as there are a couple of paths we could take.

Finally, we may wish to consider the possibility of using the generic ES cluster at PHX1 instead of a local instance on the Jenkins machine itself.  Any thoughts on this topic, :solarce ?

Comment 2

[Brandon Burton [:solarce]]

Jenkins itself doesn't use ES, individual Jenkins jobs will interact with it use it as part of the test suite.

I am building a new jenkins-services node that I'll use the newlasticsearch module on, and then work with individual test authors to migrate their tests to the new hostname

Comment 3

[Daniel Maher [:phrawzty]]

Fwiw, "latest" ES is now the 0.20.x series.  There is a 0.20.2 package in the Mozilla repo now (along with the others, including 0.19.11 which is the version on our newer webops clusters).

Comment 4

[Daniel Maher [:phrawzty]]

I've put ES 0.20.5 in the Mozilla repo; please be aware that the 0.20.x series requires Java 7 (also available in the repo: java-1.7.0-openjdk).

Comment 5

[Brandon Burton [:solarce]]

I've installed ES 0.20.x on jenkins-services1.dmz.phx1 and it is happy.