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

Timers executed twice during rebalance #34

Open
esatterwhite opened this issue May 5, 2019 · 0 comments
Open

Timers executed twice during rebalance #34

esatterwhite opened this issue May 5, 2019 · 0 comments
Labels
bug transports Transport related issues

Comments

@esatterwhite
Copy link
Owner

There is a race condition that can happen during a rebalance that will result in a timer being executed twice.

During a rebalance, all of the in-memory timers are cancelled and purged from storage. However, because transports don't have any knowledge of a shutdown or rebalance, a timer executes before it is cancelled or determined to be moved, it will be executed locally on the node, and on the remote node when it arrives.

@esatterwhite esatterwhite added bug transports Transport related issues labels May 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug transports Transport related issues
Projects
None yet
Development

No branches or pull requests

1 participant