Project

Profile

Help

Story #8291

As a user, I can configure WORKER_TTL

Added by bmbouter 5 months ago. Updated 5 months ago.

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

100%

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.

Associated revisions

Revision 87366f05 View on GitHub
Added by mdellweg 5 months ago

Turn WORKER_TTL into a setting

The heartbeat rate will scale proportional to that timeout.

fixes #8291

Co-authored-by: bmbouter

History

#1 Updated by bmbouter 5 months ago

  • Sprint/Milestone set to 3.11.0

#2 Updated by mdellweg 5 months ago

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

#3 Updated by pulpbot 5 months ago

  • Status changed from ASSIGNED to POST

#4 Updated by ipanova@redhat.com 5 months ago

  • Sprint set to Sprint 91

#5 Updated by mdellweg 5 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#6 Updated by ipanova@redhat.com 5 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF