Skip to content

Conversation

@ch3lo
Copy link
Contributor

@ch3lo ch3lo commented Aug 19, 2015

Registrator doesn't have resilience in the startup when you are trying to connect to an offline or starting up backend.

In my use case I'm using docker-compose to get my dev-cluster with consul and consul-template up, but I have some troubles when registrator run first than Consul.

I added two parameters:

  • retry-attempts, with a default value of 0 to hold backward compatibility.
  • retry-interval, with a default value of 2000 ms

bridge/types.go Outdated
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think these are needed any longer.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, you are right

@progrium
Copy link
Contributor

Looks pretty good now, just remove those fields which are no longer needed right?

progrium added a commit that referenced this pull request Sep 1, 2015
Retries to backend in the startup
@progrium progrium merged commit 8f473cb into gliderlabs:master Sep 1, 2015
This was referenced Jun 25, 2018
Closed
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.

2 participants