Project

Profile

Help

Story #8291

As a user, I can configure WORKER_TTL

Added by bmbouter 9 days ago. Updated 8 days ago.

Status:
POST
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 91
Quarter:

Description

Currently the worker timeout is hard coded to 30 seconds. In environments where volume backing Postgresql has its I/O saturated, it's been observed that even an idle system can have its workers timeout.

Solution

Move the WORKER_TTL setting to settings.py and document it. It will default to 30 seconds, which is the same value it is today.

History

#1 Updated by bmbouter 9 days ago

  • Sprint/Milestone set to 3.11.0

#2 Updated by mdellweg 8 days ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to mdellweg

#3 Updated by pulpbot 8 days ago

  • Status changed from ASSIGNED to POST

#4 Updated by ipanova@redhat.com 8 days ago

  • Sprint set to Sprint 91

Please register to edit this issue

Also available in: Atom PDF