Currently we use PostgreSQL for reports in the Socorro web UI, such as "Top Crashers", for example: https://crash-stats.mozilla.com/topcrasher/byversion/Firefox/5.0a2 Behind the scenes, this uses the "top crash by signatures" table in PostgreSQL. This bug is to track exploring Elastic Search to replace this (and other) reports, and also to investigate new features like faceted search.
Depends on: 665251
Depends on: 665562
Depends on: 673728
Depends on: 672405
Depends on: 674068
Depends on: 674420
Component: Socorro → General
Product: Webtools → Socorro
Hardware: x86_64 → All
Target Milestone: 2.0 → 2.5.2
Summary: add Elastic Search support to Socorro [tracker] → [tracker] add Elastic Search support to Socorro
To test search with elasticsearch on production, here is what you can do: 1. go to advanced search https://crash-stats.mozilla.com/query?advanced=1 2. run any search you want 3. once the results appear, add `&_force_api_impl=elasticsearch` at the end of the URL and reload 4. you should now get results coming directly from elasticsearch. One easy way of telling it does indeed come from ES is to verify that the number of results is lesser than 1,000 5. if you find a bug, please file! https://bugzilla.mozilla.org/enter_bug.cgi?product=Socorro&component=Middleware Important note: at the moment, filtering by version is broken! A pull request is open to fix that, https://github.com/mozilla/socorro/pull/1199 (bug 838897)
Other note: if you run a new search after having loaded a forced search, the new search won't be using elasticsearch and you will have to force it again by doing step 3.
retargeting this tracker for the future. not sure if its time to resolve it or not.
Target Milestone: 41 → Future
Let's mark this resolve when we have turned elasticsearch on the main production web app. Should happen when we turn the PHP app off.
The PHP app was switched off, the django app is on, elasticsearch is on!
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: Future → 51
You need to log in before you can comment on or make changes to this bug.