Closed
Bug 811300
Opened 12 years ago
Closed 12 years ago
[research] Plan upgrade to ES 0.19.11
Categories
(support.mozilla.org :: Search, defect, P1)
support.mozilla.org
Search
Tracking
(Not tracked)
RESOLVED
FIXED
2012Q4
People
(Reporter: rrosario, Assigned: rrosario)
Details
(Whiteboard: u=dev c=search p=1 s=2012.22)
IT has set up a new ES cluster with the latest version of Elastic Search. We believe there are some backwards incompatible changes that we have to deal with. This bug is about figuring out what they are and how to deal with them (file new bugs).
Assignee | ||
Updated•12 years ago
|
Priority: -- → P1
Assignee | ||
Comment 1•12 years ago
|
||
I am going to give ES latest a spin today.
Assignee: nobody → rrosario
Comment 2•12 years ago
|
||
I look forward to your conclusions.... Hopefully there aren't any issues or the issues are in ElasticUtils and not in pyes.
Assignee | ||
Comment 3•12 years ago
|
||
Here is what I found: ES v0.19.8 I've been using this version for local dev for a while and it works great for us. ES v0.19.9 Running tests result in a bunch of: IndexMissingException: [_all] missing ES v0.19.10 All tests pass. ES v0.19.11 All tests pass. I also did a full reindex and everything looks good. IT wants to put us on v0.19.11 and has a dev cluster ready for us. So I think we can proceed and try it out.
Assignee | ||
Comment 4•12 years ago
|
||
I am going to close this out. No followup bugs need to be filed at this point \o/
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 5•12 years ago
|
||
Thank you so much for doing this! I'll add an issue to the elasticutils github issue tracker about checking whether it works with 0.19.9 and documenting issues.
You need to log in
before you can comment on or make changes to this bug.
Description
•