Closed Bug 1186945 Opened 9 years ago Closed 9 years ago

Increase timeout between webapp and middleware

Categories

(Socorro :: Infra, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: adrian, Unassigned)

References

Details

When I try to update or create a new field in the Super Search Fields list, the middleware service has to verify that the new mapping works. To do that, it makes a fake index and reindex 100 documents from our current dataset. The problem is, that's a bit long, and I am getting timeouts. 

The problem with those timeouts is that the action does succeed, but the cache in the webapp does not get cleaned because it thinks the action has failed. 

Talking with Peter, we think that the problem lies between django and the middleware, probably in whatever web server is in there (nginx? ). Would it be possible to increase the timeout there? What is it currently?
Blocks: 1184709
Blocks: 1180831
Blocks: 1185400
To whom it concerns,
Adrian and I are working on stopping to use the middleware for all ES related queries. Instead we're going to make the webapp talk directly to ES (by importing socorro.external.es.supersearch). That'll make this bug moot. But it's still a week or two away. Maybe more. 
So if it's really easy to fix, let's just change whatever number we have to something slightly larger.
The nginx configs are in here:

https://github.com/mozilla/socorro-infra/tree/master/puppet/modules/socorro/files/etc_nginx/conf_d

Maybe the middleware uwsgi_read_timeout needs to be increased? Looking at the nginx log when the timeout happens would probably give a good clue.
This is taken care of.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.