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.

Sign up for GitHub

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

Jump to bottom

clientv3/concurrency/session TTL is 60s which is too long for some use-cases #5989

Closed

ekle opened this issue Jul 19, 2016 · 1 comment

Milestone

ekle commented Jul 19, 2016

at the moment the session TTL is hard-coded to 60s (https://github.com/coreos/etcd/blob/master/clientv3/concurrency/session.go#L27)
this value should be configurable as 60s are too long for some use-cases, to detect a offline node.

xiang90 assigned heyitsanthony

xiang90 added this to the v3.1.0 milestone

xiang90 mentioned this issue

clientv3: making session ttl configurable #6080

Closed

heyitsanthony mentioned this issue

Dose Mutex lock with ttl? #6111

Closed

Contributor

xiang90 commented Aug 15, 2016

Fix by #6172

xiang90 closed this as completed

philips unassigned heyitsanthony

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment