18

Is the Logstash configuration reloaded every time the agent is restarted? It doesn't seem to pick up my changes immediately (e.g. changed type value)

I'm running it with an embedded elasticsearch v.0.90.7 on Windows 7 and Kibana 3.

Thank you very much!

Regards, Paul

Paul
  • 588
  • 1
  • 4
  • 16

3 Answers3

16

Hot Reload is not yet supported. There is a Issue.

The logstash configuration is loaded at startup, so, if you kill your process (to restart it later), there is no reason why it does not work.

Ban-Chuan Lim
  • 7,840
  • 4
  • 35
  • 52
yesnault
  • 890
  • 8
  • 10
  • 5
    The issue you linked is overkill for @Paul's use case. The issue is the java startup time -- on the system I'm working on today, it takes 13 seconds to start up. Ideally the logstash process would follow the common Unix pattern and accept a HUP signal (`kill -HUP `) to trigger it to reload its configuration and rebuild the pipelines. – David Pope Jun 21 '14 at 14:19
5

Good news! Dynamic config reloading is currently scheduled for release with Logstash 2.3+(https://www.elastic.co/blog/logstash-lines-2016-02-09)! Just use --reload-interval or send a SIGHUP to reload the config!

Andrew Cholakian
  • 4,392
  • 3
  • 26
  • 27
  • Warning: In regards to Andrew's response, sending a SIGINT to the logstash process as of version 2.2 will terminate the process, not reload the configuration. – Norman B. Lancaster Mar 23 '16 at 14:02
  • Apologies, my mistake with the versions here. We are targeting 2.3 for this feature which should be coming out shortly. The signal will be SIGHUP not SIGINT. Thank you for pointing this out. – Andrew Cholakian Mar 28 '16 at 23:40
2

Seems to be available in Logstash 5: https://www.elastic.co/guide/en/logstash/current/reloading-config.html

Slava V
  • 16,686
  • 14
  • 60
  • 63