Design proper shutdown logic of all the components
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 29
- Forks
- 30
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 6
Description
We need to properly define how to shutdown all the components. There is an inter-dependency of the sub components (for example, repl services during commit can be referencing cp_mgr but cp_mgr is reset before repl_service is shutdown). We need to define a proper way of stopping all the activity in all components before triggering shutdown
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 mapping the shutdown paths for the REPL services and cp_mgr, focusing on the commit-time dependency described in the issue. Define and document an ordering that stops component activity before dependent state is reset; done means all components shut down without active references to already-reset components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100