1062342 - update PHX Elasticsearch cluster to 1.2.x for Input and SUMO

Status: RESOLVED FIXED

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

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

Elasticsearch made some big API changes between 0.90 and 1.0. All their libraries work with Elasticsearch 1.0+ and no longer work with 0.90. That makes development work difficult.

Can we update the Elasticsearch cluster to 1.0 or 1.1 for Input?

Comment 1

[C. Liang [:cyliang]]

If possible, I'd like to update to at least 1.2.x or 1.3.x, given the vulnerability disclosures around previous 1.x versions. [1]  However, I'm not sure if disabling dynamic scripting is going to cause some serious repercussions.  

I can start a chain of bugs to upgrade the shared ES clusters but probably won't be able to give it much effort until next week.  Will that time frame work for you? 


[1] http://www.elasticsearch.org/blog/scripting-security/

Comment 2

[Will Kahn-Greene [:willkg] ET needinfo? me]

Most of us (Input, SUMO, Mozillians, etc) use ElasticUtils. The latest version of that goes to great lengths to support 0.90, 1.0 and 1.1 of Elasticsearch. It's pretty messy, but my theory was that everyone switches to that version, then we upgrade Elasticsearch to 1.1 and then we can upgrade ElasticUtils to a future version that doesn't support 0.90 anymore and thus is easier to maintain.

I had difficulties making it also support Elasticsearch 1.2. I'll spend some more time on that and see if I can get over the hurdles I hit.

Rob says Marketplace is using Elasticsearch 1.2 and they don't yet have a need for dynamic scripts. So I think disabling that is probably fine. We'd have to ask the owners of the other projects that use that cluster to know if they need it or not.

Comment 3

[Will Kahn-Greene [:willkg] ET needinfo? me]

I'm going to try to get ElasticUtils working with Elasticsearch 1.2 this week. I just haven't had time, yet. The reasons you gave in comment #1 to jump to 1.2 make a lot of sense to me.

Can you give me a few more days before we go ahead with this?

Comment 4

[Will Kahn-Greene [:willkg] ET needinfo? me]

I spent this morning working on ElasticUtils and got it working fine with Elasticsearch 1.2.

Given that, I'm game for pushing forward to Elasticsearch 1.2.

Comment 5

[Will Kahn-Greene [:willkg] ET needinfo? me]

Rather than file another bug for SUMO, I'm adding SUMO to the summary.

Input is currently using Elasticsearch 1.2.4 on the dev cluster which means our -stage environment doesn't match our -prod environment in some significant ways. That's a rough place to be. Definitely makes me nervous to the point where I've been pushing off all Elasticsearch-related development.

Where are we at right now? Is there anything I can do to help move things along? Are there other bugs that are in progress that I don't know about and/or aren't referenced in this bug?

Comment 6

[Will Kahn-Greene [:willkg] ET needinfo? me]

Making this block on the actual webops work bug.

Comment 7

[C. Liang [:cyliang]]

The PHX1 production ES cluster has been  upgraded to version 1.2.4.