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

support for config reload #5

Open
cusspvz opened this issue May 27, 2015 · 1 comment
Open

support for config reload #5

cusspvz opened this issue May 27, 2015 · 1 comment

Comments

@cusspvz
Copy link

cusspvz commented May 27, 2015

Is there any chance, with current architecture, to create a feature that reloads configs on-the-fly?

@jondubois
Copy link
Member

@cusspvz It doesn't support it right now, but it's definitely possible to add this feature. Pull requests are welcome. Maybe we can make the master process listen for a SIGUSR2 signal (or other) and when it receives one, it can read the config.json file again and pass the latest config JSON to the workers.

Or maybe the master process can have its own TCP 'command server' and we can just send it the new config data via TCP and then it passes it on to workers.

Not sure what's best practice here so suggestions welcome.

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

No branches or pull requests

2 participants