spring-projects / spring-projects/spring-pulsar
Graceful/StopImmediate shutdown
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 205
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
What is the implication of this interrupt if the batch receive is in the middle of a batch of records? I understand the need for this when the timeout is high - but it also feels like maybe this would be an operation we did when the user asked to "stopImmediately" vs. "stopGracefully". Does this need to be included in this proposal or added when if we add a stopImmediately/Gracefully feature?
Either way, a comment would help understand the purpose of the interrupt.
Originally posted by @onobc in https://github.com/spring-projects-experimental/spring-pulsar/pull/162#discussion_r994039488
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
The issue names no source file or test; begin with the referenced discussion in spring-pulsar PR 162 and trace the batch-receive shutdown and interrupt behavior. Done means resolving whether this belongs in the current proposal or a separate stopImmediately/stopGracefully feature, with the purpose of the interrupt documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100