-
-
Notifications
You must be signed in to change notification settings - Fork 243
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
restart followed by reload is unnecessary #438
Milestone
Comments
@moofish32 Thank you for pointing on this! You're right - we actually have two subsequent actions with Consul service on the initial bootstrap:
And that should be fixed. I'll look into it soon. |
Fixed by #443 |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The default recipe currently sets up a situation in which restart is called followed immediately by reload. Is there a benefit here? The disadvantage is that in RHEL 6.9 consul actually fails to start because these are called back to back for me. I would say it's definitely a race condition but seems to be about 8 out of 10 so far.
If we make this a restart, then only one action is taken and I think everything works.
https://github.com/johnbellone/consul-cookbook/blob/master/recipes/default.rb#L21
The text was updated successfully, but these errors were encountered: