Make router do a best-effort completion of active operations during a shut down
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
`OperationController`s does not make any attempts to complete active operations when a shutdown is issued today. This can be improved. The `OperationController` can make note of the fact that the shutdown has been called and stop accepting new operations. But it can wait a few seconds for any active operations to complete (if there are any).
This came out of the discussion on #298
Contributor guide
No contributing guide indexed for this repository
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 reading the OperationController entry point and the discussion in issue #298. Determine how shutdown and active operations are currently handled, then define the waiting behavior and timeout for best-effort completion. Done means shutdown stops new operations while allowing active operations a few seconds to finish.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100