Support reloading the configuration file with SIGHUP

[jsternberg]

Feature Request

Support the standard reloading of a configuration file with SIGHUP for anything that would be reasonable.

Proposal: Support reloading the configuration file with SIGHUP.

Current behavior: You must restart InfluxDB to load new configuration options.

Desired behavior: Configuration values that are easy to change (such as log levels or query limits) without requiring a potentially long restart.

Use case: It allows a DevOps person to be able to update certain settings when tuning the database without downtime.

[candlerb]

Relates to https://github.com/influxdata/telegraf/issues/69

[Darkentik]

Relates to influxdata/telegraf#69

You missunderstand him. He not wanted to reload the telegraf instead of the database influxdb. this is a feature we need too. I always have to restart the complete influxdb service and this ends up with some downtimes of the influxdb. Or does this exists already? I didn´t found something in the docs.

[candlerb]

By "relates" I meant "similar feature requested in a different component of the TICK stack"

[galindro]

I need this feature too because I'm using letsencrypt to generate influxdb certificates and a reload configuration could be used to load the new certificate, avoiding database downtime.

[Genda1ph]

I'm bewildered how this still hasn't been implemented. Is there a different way for online configuration change?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Genda1ph]

Not having any activity doesn't mean it's not important.

[phgogo]

This is a feature i expect in an production-ready application!

[m82labs]

Putting a vote in for this as well.

[ruairinewman]

We would definitely like to see this implemented also. With production cluster nodes taking as long as 4 hours to complete a restart due to the volume of data we hold, this would avoid many problems.

[m82labs]

We would definitely like to see this implemented also. With production cluster nodes taking as long as 4 hours to complete a restart due to the volume of data we hold, this would avoid many problems.

Just curious, but how much data do you have? I have about 1TB and a service restart takes about 5 minutes. Interested to know when I might get to 4 hour territory.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Genda1ph]

bump

[lhanson]

Bumping again because it seems incredible that I can't update configuration without downtime.

[foobar]

any response from maintainers?

[fdgod09]

bump

[anandpathak]

bumping! this is a must-have feature

[fmr-ap]

bump

[suhlig]

I'd like to have this.

[MonilCereBulb]

+1

[TiagoMHCSantana]

+1

[Guzya]

+1

[sobos-office]

+1

[hardincm2]

+1

[Technoguyfication]

This is a big problem for me, I have to automatically restart influx whenever my SSL cert renews. I'm able to reload nginx with new certs each time, so why can't I reload influx?

[danielelopez1]

+1

[sdrsdr]

+1

[dbivolaru]

+1

[emilbasv3]

+1 This is a must have for a production ready product.

[joelsdc]

I have to admit I was surprised to see this issue still open from 2016, I would have expected to have a way to reload SSL certs since day 1.

As a workaround, we've added our load balancers (Kong) in the path to reach influxdb, but it would be nice to not have to proxy requests just for SSL.