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

Restart service instead reload as only few configurations are reloadble. #341

Closed
vijaybandari opened this issue Aug 24, 2016 · 3 comments
Closed

Comments

@vijaybandari
Copy link

vijaybandari commented Aug 24, 2016

Reload works only for few set of configurations as mentioned here.
https://www.consul.io/docs/agent/options.html#reloadable-configuration

https://github.com/johnbellone/consul-cookbook/blob/master/recipes/default.rb#L45
It should be restart instead of reload.

@legal90
Copy link
Contributor

legal90 commented Aug 24, 2016

Hi @vijaybandari
That was done intentionally by 80f4a1c and #309
Please, refer to the discussion: #288

TL;DR: Automatic restart of Consul servers could cause a cluster downtime when you run chef-client simultaneously on your nodes. Also, if Consul version has been changed (upgrade scenario), then Consul servers should be restarted manually, according to the upgrade manual.

@vijaybandari
Copy link
Author

Thanks @legal90 , now it makes sense.

@lock
Copy link

lock bot commented Apr 25, 2020

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.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants