Project

Profile

Help

Task #2370

re-evaluate the time interval values used by Pulp for deciding when components are dead

Added by dkliban@redhat.com almost 3 years ago. Updated 6 months ago.

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

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

We should consider lowering the threshold for considering components of Pulp as being dead. Most of the values are defined here0. The goal is to reduce the amount of time a failover takes. The goal is to be somewhere between 2 and 3 minutes.

[0] https://github.com/pulp/pulp/blob/3.0-dev/tasking/pulp/tasking/constants.py


Checklist

History

#1 Updated by bmbouter almost 3 years ago

  • Checklist item update the failover times for the resource manager added
  • Checklist item update the failover times for the celerybeat service added

#2 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF