1010239 - [tracker] Move to Elasticsearch version 1.x

Status: RESOLVED FIXED

(Socorro :: General, task)

Description

[[DEACTIVATED] Adrian Gaudebert]

If possible, go to 1.1 directly, otherwise upgrade to 1.0.

Comment 1

[[DEACTIVATED] Adrian Gaudebert]

:phrawzty has been taking notes here: https://etherpad.mozilla.org/bug1010240

Comment 2

[[DEACTIVATED] Adrian Gaudebert]

The investigation is complete and is summarized here: https://bugzilla.mozilla.org/show_bug.cgi?id=1010240#c1. Follow-up bugs have been filed, action will be taken.

Comment 3

[Daniel Maher [:phrawzty]]

https://etherpad.mozilla.org/bug1010239--ES-upgrade-plan

Comment 4

[Daniel Maher [:phrawzty]]

(In reply to Adrian Gaudebert [:adrian] from comment #0)
> If possible, go to 1.1 directly, otherwise upgrade to 1.0.

Addendum: If possible, go to *1.4* directly...

Comment 5

[Daniel Maher [:phrawzty]]

We're *not* going to do this in PHX1 - there's just no point since we're going to be abandoning that DC in any case.  All of our new AWS-based infra targets ES 1.4 from the get-go.

Not sure where that leaves this bug.  Needinfo'ing...

Comment 6

[[DEACTIVATED] Adrian Gaudebert]

Can we get 1.5 instead? It's new hotness. 

Let's keep this bug around as a "we are on ES 1.x" tracker. Renaming a bit.

Comment 7

[Daniel Maher [:phrawzty]]

(In reply to Adrian Gaudebert [:adrian] from comment #6)
> Can we get 1.5 instead? It's new hotness. 
> 
> Let's keep this bug around as a "we are on ES 1.x" tracker. Renaming a bit.

I don't trust x.0 releases, to be honest; I'd rather we continue to aim at 1.4.x until 1.5 gains some maturity.

Comment 8

[Peter Bengtsson [:peterbe]]

All dependents resolved.