As a user, content app can be shut down quickly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: @goosemania (ttereshc)
Redmine Issue: 8956, https://pulp.plan.io/issues/8956
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
- I shut down the content app workers
- I check the status API immediately after and it shows there are no workers
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the content app heartbeat, its shutdown path, and the status API; the issue does not name specific files or tests. Confirm the expected graceful-shutdown behavior and ensure the status API reflects that content app workers are offline immediately after shutdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100