Determine appropriate proxy_read_timeout setting for Tools Proxy
Open, MediumPublic
Actions

Assigned To

None

Authored By

	• chasemp
	Apr 19 2017, 10:22 PM

Description

proxy_read_timeout was set to 3600s (1h) from 600s (10m) to handle a PAWS specific case but seems to be potentially interferring with nginx releasing workers and resources. I can't find an example of anyone setting this to greater than 10m and based on our recent experiences with being unable to run nginx reload for graceful user impact I think we should reduce.

https://gerrit.wikimedia.org/r/#/c/256882/5/modules/dynamicproxy/templates/nginx.conf

Related Objects

Mentioned Here: T120335: Terminal gets 'stuck' after a few minutes without activity

Event Timeline

• chasemp created this task.Apr 19 2017, 10:22 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 19 2017, 10:22 PM

• chasemp triaged this task as Medium priority.Apr 19 2017, 10:22 PM

• chasemp updated the task description. (Show Details)

Original task on the timeout increase from 10m to 1 hour - T120335

• madhuvishy renamed this task from Determinte appropriate proxy_read_timeout setting for Tools Proxy to Determine appropriate proxy_read_timeout setting for Tools Proxy.Apr 19 2017, 11:06 PM

• Phabricator_maintenance moved this task from Backlog to Acknowledged on the SRE board.Jan 26 2019, 9:12 PM

Krinkle added a project: Sustainability (Incident Followup).Sep 28 2021, 10:51 PM

Krinkle updated the task description. (Show Details)

Krinkle removed subscribers: • madhuvishy, • chasemp.

taavi edited projects, added Toolforge; removed SRE, Cloud-Services.Jan 30 2022, 9:43 AM

Determine appropriate proxy_read_timeout setting for Tools ProxyOpen, MediumPublicActions

Description

Related Objects

Event Timeline

Determine appropriate proxy_read_timeout setting for Tools Proxy
Open, MediumPublic
Actions