Project

Profile

Help

Story #8956

closed

As a user, content app can be shut down quickly

Added by ttereshc over 2 years ago. Updated about 2 years ago.

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

0%

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

Description

Ticket moved to GitHub: "pulp/pulpcore/2020":https://github.com/pulp/pulpcore/issues/2020


Workers support graceful shutdown, in this case the fact that workers are offline is reflected very quickly in the db.
For content app shutdown, it depends on its heartbeat and depending on the configuration of its ttl, the time of shutdown can be very noticeable.

It would be useful to support graceful shutdown, similar to the workers.
Usage example: without this improvement, pulpcore-manager commands which require services to be shutdown wait for quite some time after stopping the service.

Expected outcome

  1. I shut down the content app workers
  2. I check the status API immediately after and it shows there are no workers
Actions #1

Updated by ttereshc over 2 years ago

  • Description updated (diff)
Actions #2

Updated by bmbouter over 2 years ago

  • Description updated (diff)
Actions #3

Updated by pulpbot about 2 years ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF