If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

update kitsune to ElasticUtils 0.10.1

RESOLVED FIXED

Status

support.mozilla.org
General
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: willkg, Assigned: willkg)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Bug #1071044 covers upgrading the Elasticsearch cluster for -dev to 1.2. Before that happens, we need a version of ElasticUtils that works with the version we have now (0.90) and the version we're upgrading to (1.2).

Ergo we need to update ElasticUtils to 0.10.1 before October 2nd.
I updated Fjord to 0.10 in these two commits:

https://github.com/mozilla/fjord/commit/c4e8e345573e79d418893ea7b118c52cf968c545
https://github.com/mozilla/fjord/commit/e023fa4ed866e0d759eaa73615cf011ff7a57113

I wrote up some rough migration documentation here:

http://elasticutils.readthedocs.org/en/latest/migrating_0.90_to_1.0.html

The part about "Tricky things" covers the tricky stuff.

Updating from ElasticUtils 0.10 to 0.10.1 is just a matter of updating ElasticUtils and elasticsearch-py--there weren't any other changes required.
Grabbing this one.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
This requires a test plan. I think something like this catches most/all of the possible issues:

1. run the tests

2. run the following commands:

   ./manage.py esstatus
   ./manage.py esdelete <index listed in esstatus>
   ./manage.py esreindex --delete --percent=5
   ./manage.py esverify
   ./manage.py essearch cupcake

3. go to /en-US/ , type in a search and make sure it searches as you type

4. go to /en-US/search , type in a search and hit enter

5. go to /en-US/search?a=2 , do a search for each tab

6. go to /en-US/products/firefox

7. go to /en-US/products/firefox/get-started

8. go to /en-US/kb/update-firefox-latest-version

9. go to /en-US/questions/new and go through the whole flow

10. go to /en-US/forums and click around the forums

11. go to /en-US/contributors and make sure the four tabs on the left all work

12. go to /en-US/questions/firefox

13. go to /en-US/kpi/dashboard and make sure charts show up

14. go to /en-US/questions/dashboard/metrics

15. go to /en-US/karma/questions


Is there anything missing from this list?
Flags: needinfo?(rrosario)
You can skip 15. Replace it with:

15. go to /en-US/community and search for a user (/en-US/community/search?q=r1cky for example). Verify the top contributors show up on the right.
Flags: needinfo?(rrosario)
I think that covers it. Do we want to test out reindexing from the admin?
Oops! I completely forgot about admin related things.

Updated test plan:

1. run the tests

2. run the following commands:

   ./manage.py esstatus
   ./manage.py esdelete <index listed in esstatus>
   ./manage.py esreindex --delete --percent=5
   ./manage.py esverify
   ./manage.py essearch cupcake

3. go to /en-US/ , type in a search and make sure it searches as you type

4. go to /en-US/search , type in a search and hit enter

5. go to /en-US/search?a=2 , do a search for each tab

6. go to /en-US/products/firefox

7. go to /en-US/products/firefox/get-started

8. go to /en-US/kb/update-firefox-latest-version

9. go to /en-US/questions/new and go through the whole flow

10. go to /en-US/forums and click around the forums

11. go to /en-US/contributors and make sure the four tabs on the left all work

12. go to /en-US/questions/firefox

13. go to /en-US/kpi/dashboard and make sure charts show up

14. go to /en-US/questions/dashboard/metrics

15. go to /en-US/community and search for a user (/en-US/community/search?q=r1cky for example). Verify the top contributors show up on the right.

16. go to /admin/search-index and make sure it comes up

17. go to /admin/search-maintenance and trigger a non-destructive reindexing

18. go to /admin/search-troubleshooting and make sure it comes up

19. go to /admin/synonym_bulk and make sure it comes up


I think that covers everything.
In a PR: https://github.com/mozilla/kitsune/pull/2134
For the record, this was about 3 days of work to get to this point. I'm guessing at least another day of testing. I'm not sure how much time will be required to adequately review and fix issues.
I went through and ran all the above steps with Elasticsearch 0.90.10 (which is what we've got now) as well as Elasticsearch 1.2.4 (which is what we're upgrading to soon).
Landed in:

https://github.com/mozilla/kitsune/commit/ad09de5aef5779c832bae46ffffcb0740a6633b9
https://github.com/mozilla/kitsune/commit/6b75d7cddc274776a8b908d34d3cf3386b7bdcd4
Pushed to prod just now. Everything looks ok, so I'm marking this as FIXED. I'll keep an eye out for any problems that might arise and fix them ASAP P1 PRONTO FIRSTP0ST!
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(In reply to Will Kahn-Greene [:willkg] from comment #11)
> Pushed to prod just now. Everything looks ok, so I'm marking this as FIXED.
> I'll keep an eye out for any problems that might arise and fix them ASAP P1
> PRONTO FIRSTP0ST!

FWIW, ran both our staging and production automation throughout, and both are happy -- just as a datapoint :-)
You need to log in before you can comment on or make changes to this bug.