-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Instantiate the RemoteClusterWatcher with gatewayAlive=true (#8590) #8725
Conversation
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.
Thank you for the PR! I don't think there's any need to test this. Have you checked whether this fixes your problem?
@@ -204,6 +204,8 @@ func restartClusterWatcher( | |||
repairPeriod, | |||
probeWorker.Liveness, | |||
enableHeadlessSvc, | |||
// always instantiate the gatewayAlive=0 to prevent unexpected service fail fast |
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.
nit: would it make more sense for gatewayAlive=1
here? generally true evaluates to the constant 1, and false to 0.
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.
Sorry for the mistake, I'll correct this comment.
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.
No problem! :)
@mateiidavid I've publish this change to our cluster, but there's no watch restart yet. I'll give you the confirmation in maybe 12 hours. |
If we don't instantiate the RemoteClusterWatcher with gatewayAlive=true, then there will be a small period all services will fail-fast unexpectedly. Simply Instantiate the RemoteClusterWatcher with gatewayAlive=true. Fix #8590 Signed-off-by: Ao Chen <chenao3220@gmail.com>
@mateiidavid Confirmed, the watch restarting happens and there's no service fail fast. It fixes my problem. |
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.
Great! Thanks @chenaoxd
If we don't instantiate the RemoteClusterWatcher with gatewayAlive=true, then there will be a small period all services will fail-fast unexpectedly. Simply Instantiate the RemoteClusterWatcher with gatewayAlive=true. Fix #8590 Signed-off-by: Ao Chen <chenao3220@gmail.com>
If we don't instantiate the RemoteClusterWatcher with gatewayAlive=true, then there will be a small period all services will fail-fast unexpectedly. Simply Instantiate the RemoteClusterWatcher with gatewayAlive=true. Signed-off-by: Ao Chen <chenao3220@gmail.com>
If we don't instantiate the RemoteClusterWatcher
with gatewayAlive=true, then there will be a small
period all services will fail fast unexpectedly.
Simply Instantiate the RemoteClusterWatcher with
gatewayAlive=true.
Fix #8590
Signed-off-by: Ao Chen chenao3220@gmail.com