-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 etcd calls exception handling and adjust failure detection timeout #18554
Fix etcd calls exception handling and adjust failure detection timeout #18554
Conversation
…when refresh the workers view instead of propagate throwing all the way to the caller 2. make worker failure detection timeout (the timeout to determine if a worker is in FAILED state) configurable thru setting the service discovery entity's lease ttl 3. make newLeaseInternal always overwrite the key with the newly created lease
…KER_FAILURE_TIMEOUT_IN_MILLIS
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. Thanks for the works!
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
@@ -68,11 +74,11 @@ public class MembershipManagerTest { | |||
/* | |||
@BeforeClass | |||
public static void init() { | |||
PropertyConfigurator.configure("alluxio/conf/log4j.properties"); | |||
PropertyConfigurator.configure("/Users/lucyge/Documents/github/alluxio/conf/log4j.properties"); |
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.
notice that the absolute path contains your own information
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.
ah good catch thanks!
alluxio-bot, merge this please. |
What changes are proposed in this pull request?
Why are the changes needed?
To resolve:
Does this PR introduce any user facing changes?
No