-
Notifications
You must be signed in to change notification settings - Fork 215
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
fix: change namespace starts processor on namespace change even if not leader #2344
Conversation
…t leader Signed-off-by: Attila Mészáros <[email protected]>
Would be a bit nicer to check if the instance is the leader, but in the current scope controller is unaware of the leader election, - - which is not necessarily bad layering, actually kinda of makes nice loose coupling. Will add tests, before marking it ready. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
if (eventProcessorWasRunning) { | ||
eventProcessor.start(); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could it happen that at this point we are are already the leader (and accidentally not start processing) or the synchronised
will take care of that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
exactly, synchronized
takes care of that
Signed-off-by: Attila Mészáros <[email protected]>
No description provided.