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.

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

Retry heartbeat after initial service registration #247

Merged

Conversation

tgross
Copy link
Contributor

@tgross tgross commented Nov 18, 2016

For #225

Sending a heartbeat to a not-yet registered service fails on both the discovery/consul and discovery/etcd backends. Previously we'd catch the error, register the service, and return so that we'd send a passing heartbeat on the next health check poll. This change retries the heartbeat on the newly registered service so that we become healthy more quickly.

cc @misterbisson @jasonpincin @justenwalker

Sending a heartbeat to a not-yet registered service fails on both the
`discovery/consul` and `discovery/etcd` backends. Previously we'd catch
the error, register the service, and return so that we'd send a passing
heartbeat on the next health check poll. This change retries the
heartbeat on the newly registered service so that we become healthy more
quickly.
@tgross tgross merged commit 230f651 into TritonDataCenter:master Nov 29, 2016
@tgross
Copy link
Contributor Author

tgross commented Nov 29, 2016

@tgross tgross deleted the gh225_healthy_on_1st_heartbeat branch April 4, 2017 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant