Skip to content
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

Retrospectively change the meaning of halt on WorkProcessor #322

Merged
merged 3 commits into from
Nov 18, 2020

Conversation

Palmr
Copy link
Member

@Palmr Palmr commented Nov 13, 2020

Our previous intermittency fix changed the meaning of WorkProcessor::halt and we should have updated the documentation to reflect that breaking change.

@Palmr
Copy link
Member Author

Palmr commented Nov 13, 2020

With this change we should also look at the re-startable nature of WorkerPool which holds the WorkProcessor instances.
This will get upset when re-starting as any previously-halted WorkProcessor will no longer be able to start.

@grumpyjames
Copy link
Member

This looks fine, merge is imminent - I'll open a separate issue about the future of WorkerPool et al

@grumpyjames grumpyjames merged commit 3530a12 into LMAX-Exchange:master Nov 18, 2020
@Palmr Palmr added this to the 4.0 milestone Dec 4, 2020
@Palmr Palmr linked an issue Dec 4, 2020 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
4.0
Awaiting triage
Development

Successfully merging this pull request may close these issues.

Evict WorkerPool et al from core of disruptor
2 participants