-
Notifications
You must be signed in to change notification settings - Fork 482
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
Update lib dependencies and add some small fixes #189
Conversation
…added to ensure we get an error returned on dial failure
Pull Request Test Coverage Report for Build 1449865424
💛 - Coveralls |
sd.etcdDialKeepAliveTime = sd.config.GetDuration("pitaya.cluster.sd.etcd.dialtimeout") | ||
sd.etcdDialKeepAliveTimeout = sd.config.GetDuration("pitaya.cluster.sd.etcd.dialtimeout") |
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.
We should be using pitaya.cluster.sd.etcd.dialkeepalivetime
and pitaya.cluster.sd.etcd.dialkeepalivetimeout
here, like in config/config.go
, right?
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.
yep, this is just adding to all locations this new configuration option, it's basically a built-in mechanism in etcd client to check if the connection is alive https://github.com/etcd-io/etcd/blob/7ea5ee8b5dcdceb5a26a5c1dfe7ca290000a007b/client/v3/config.go#L39
This isn't required for the fixes, it was just adding some extra configurability
No description provided.