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

Consul service should restart instead of reload #307

Closed
miroswan opened this issue Apr 6, 2016 · 3 comments · Fixed by #309
Closed

Consul service should restart instead of reload #307

miroswan opened this issue Apr 6, 2016 · 3 comments · Fixed by #309

Comments

@miroswan
Copy link

miroswan commented Apr 6, 2016

If I make a change to a config, it doesn't show in the API or UI until I actually restart the service. Reload doesn't seem to suffice.

@wstaples
Copy link

wstaples commented Apr 7, 2016

Hi @miroswan,

Can you tell us what configuration change you are making that doesn't seem to reload?
I assume you are reloading the service and not using the CLI consul reload
According to the docs These are the only re-loadable items

Reloadable Configuration

Reloading configuration does not reload all configuration items. The items which are reloaded include:

-Log level
-Checks
-Services
-Watches
-HTTP Client Address
-Atlas Token
-Atlas Infrastructure
-Atlas Endpoint

@legal90
Copy link
Contributor

legal90 commented Apr 14, 2016

@miroswan Automatic consul daemon restart could be really harmful. Please refer to the discussion #288

@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

Successfully merging a pull request may close this issue.

3 participants