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

Fix reload of retry_join server addresses on SIGHUP #1566

Merged
merged 1 commit into from
Aug 12, 2016
Merged

Fix reload of retry_join server addresses on SIGHUP #1566

merged 1 commit into from
Aug 12, 2016

Conversation

mlafeldt
Copy link
Contributor

@mlafeldt mlafeldt commented Aug 11, 2016

The current code does not update the actual config, but only the local reference to it.

/cc @denderello

@mlafeldt
Copy link
Contributor Author

Speaking of config reloading, it looks like retry_join is the only setting currently updated by SIGHUP. Is this correct?

Also, I think it makes sense to implement the same logic for clients, so that they can be notified about new servers as well. What do you think?

@mlafeldt mlafeldt changed the title Fix reload of retry_join server address on SIGHUP Fix reload of retry_join server addresses on SIGHUP Aug 11, 2016
The current code does not update the actual config, but only the local
reference to it.
@mlafeldt
Copy link
Contributor Author

Regarding client retries: I checked the source code and reloading the list of servers via SIGHUP seems to be a bigger task since clients register with servers via RPC (buried deep down in the client code). Reloading is only really supported via Consul, it seems.

@diptanu
Copy link
Contributor

diptanu commented Aug 12, 2016

Merging this change. Thanks! And yeah, it will probably need more work for the clients to refresh the list of servers via SIGHUP

@diptanu diptanu merged commit 880fbee into hashicorp:master Aug 12, 2016
@mlafeldt mlafeldt deleted the fix-config-reload branch August 12, 2016 12:16
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 18, 2023
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 this pull request may close these issues.

None yet

2 participants