Don't cache supersearch fields

RESOLVED FIXED

Status

Socorro
Webapp
RESOLVED FIXED
5 months ago
5 months ago

People

(Reporter: peterbe, Assigned: peterbe)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

5 months ago
In the olden days we used to store all supersearch fields in ES. 
Now we're storing them in a .json file on disk. 

Because the ES lookup was higher latency than cache we used to cache the read supersearch fields for 24h [0].
That long time was OK because when the supersearch fields was entirely managed through the webapp admin pages, it would invalidate the cache each time there was a db write. 

Let's ditch the cache entirely. 

[0] https://github.com/mozilla-services/socorro/blob/master/webapp-django/crashstats/supersearch/models.py#L226

Comment 2

5 months ago
Commit pushed to master at https://github.com/mozilla-services/socorro

https://github.com/mozilla-services/socorro/commit/d6ecf522f4f93352b0302bc149bd599238b6451c
Bug 1393181 dont cache supersearch fields (#3937)

* fixes bug 1393181 - Don't cache supersearch fields

* doc cleanup
(Assignee)

Comment 3

5 months ago
That commit should have closed this bug. Strange that it didn't.
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.