-
Notifications
You must be signed in to change notification settings - Fork 242
Fix global lock contention in DistClusterControllerStateModel caused by Optional.empty() singleton
#3052
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
base: master
Are you sure you want to change the base?
Fix global lock contention in DistClusterControllerStateModel caused by Optional.empty() singleton
#3052
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -40,6 +40,9 @@ public class DistClusterControllerStateModel extends AbstractHelixLeaderStandbyS | |
| protected Optional<HelixManager> _controllerOpt = Optional.empty(); | ||
| private final Set<Pipeline.Type> _enabledPipelineTypes; | ||
|
|
||
| // dedicated lock object to avoid cross-instance contention from Optional.empty() singleton | ||
| private final Object _controllerLock = new Object(); | ||
|
|
||
| public DistClusterControllerStateModel(String zkAddr) { | ||
| this(zkAddr, Sets.newHashSet(Pipeline.Type.DEFAULT, Pipeline.Type.TASK)); | ||
| } | ||
|
|
@@ -62,7 +65,7 @@ public void onBecomeLeaderFromStandby(Message message, NotificationContext conte | |
|
|
||
| logger.info(controllerName + " becoming leader from standby for " + clusterName); | ||
|
|
||
| synchronized (_controllerOpt) { | ||
| synchronized (_controllerLock) { | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If Optional.empty() is the root cause of locking problem, why not just make the function synchronized without creating new lock object?
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Appreciate the suggestion @junkaixue, that’s a fair point. I agree that synchronized at method level on this would technically provide mutual exclusion in this case. I opted for a dedicated lock object (_controllerLock) to keep the synchronization scope narrowly focused on controller lifecycle transitions, and also I didnt want to change the already implemented dedicated lock logic. This makes the locking intent more explicit and avoids potential contention if other unrelated synchronized methods are ever added to this class (either now or later, or lets say by mistake).
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let me know what you think, if we are sure this class will be small in size in future and not much complex, then yeah synchronized methods make more sense then. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @junkaixue : a new lock based implementation is close to the existing implementation while fixing the problem on the lock contention issue found as mentioned in the issue (due to JDK implementation of Optional.empty as singleton). imho, making the methods synchronized may be of larger scope as we need to relook at the thread safety of other instance variables in current class and its base classes. So, if you suggest to fix this, should this be addressed in a different issue and PR. |
||
| if (!_controllerOpt.isPresent()) { | ||
| HelixManager newController = HelixManagerFactory | ||
| .getZKHelixManager(clusterName, controllerName, InstanceType.CONTROLLER, _zkAddr); | ||
|
|
@@ -112,7 +115,7 @@ public String getStateModeInstanceDescription(String partitionName, String insta | |
|
|
||
| @Override | ||
| public void reset() { | ||
| synchronized (_controllerOpt) { | ||
| synchronized (_controllerLock) { | ||
| if (_controllerOpt.isPresent()) { | ||
| logger.info("Disconnecting controller: " + _controllerOpt.get().getInstanceName() + " for " | ||
| + _controllerOpt.get().getClusterName()); | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.