Skip to content

GH-2482: Option for Containers to Stop Immediately #2483

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 12, 2023

Conversation

garyrussell
Copy link
Contributor

Resolves #2482

forceStop means stop after the current record and requeue all prefetched.

Just close the channel - canceling the consumer first causes a race condition which could allow another exclusive or single-active consumer to start processing while this container is still running.

Also support async stop on DMLC (previously only available on the SMLC).

cherry-pick to 2.4.x

Resolves spring-projects#2482

`forceStop` means stop after the current record and requeue all prefetched.

Just close the channel - canceling the consumer first causes a race condition which
could allow another exclusive or single-active consumer to start processing while
this container is still running.

Also support async stop on DMLC (previously only available on the SMLC).

**cherry-pick to 2.4.x**
@artembilan artembilan merged commit 1fdfe65 into spring-projects:main Jul 12, 2023
@artembilan
Copy link
Member

... and cherry-picked to 2.4.x after minor conflict resolution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ensure Strict Ordering with Single Active and Exclusive Consumers
2 participants