Skip to content
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

should I maintain a heartbeat in application layer? #7838

Closed
hzxuzhonghu opened this issue Apr 29, 2017 · 2 comments
Closed

should I maintain a heartbeat in application layer? #7838

hzxuzhonghu opened this issue Apr 29, 2017 · 2 comments

Comments

@hzxuzhonghu
Copy link

Firstly, client connect to etcd cluster, and watch for something change
then, if send a SIGSTOP signal to the etcd connected to by hand, client would not sense connection disconnect in both V2 and V3. And client still treate connection alive. beacuse tcp heartbeat still exist

Should I maitain a heartbeat every period time, and when heartbeat timeout then try another etcd endpoint?
@heyitsanthony
Copy link
Contributor

With the client as it is now, yes, that check would need application-level heart beats. Related: #7321 #7247

@heyitsanthony
Copy link
Contributor

Closing. Please reopen if you have any further questions. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hzxuzhonghu @heyitsanthony