github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-24 14:47:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

Expand section on force reloading config

Browse source 
Fixes #11699
This commit is contained in:
Karen Metts 2020-03-17 17:18:52 -04:00
parent 758bc5c620
commit 1c964a27a5
1 changed files with 11 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

17
docs/static/reloading-config.asciidoc vendored
View file

@ -1,8 +1,7 @@
[[reloading-config]]
=== Reloading the Config File
Starting with Logstash 2.3, you can set Logstash to detect and reload configuration
changes automatically.
You can set Logstash to detect and reload configuration changes automatically.
To enable automatic config reloading, start Logstash with the `--config.reload.automatic` (or `-r`)
command-line option specified. For example:
@ -19,9 +18,13 @@ By default, Logstash checks for configuration changes every 3 seconds. To change
use the `--config.reload.interval <interval>` option, where `interval` specifies how often Logstash
checks the config files for changes (in seconds).
If Logstash is already running without auto-reload enabled, you can force Logstash to
reload the config file and restart the pipeline by sending a SIGHUP (signal hangup) to the
process running Logstash, but it's not supported on Windows OS. For example:
[[force-reload]]
==== Force reloading the config file
If Logstash is already running without auto-reload enabled, you can force
Logstash to reload the config file and restart the pipeline. Do this by sending
a SIGHUP (signal hangup) to the process running Logstash.
For example:
[source,shell]
----------------------------------
@ -30,7 +33,9 @@ kill -SIGHUP 14175
Where 14175 is the ID of the process running Logstash.
==== How Automatic Config Reloading Works
NOTE: This functionality is not supported on Windows OS.
==== How automatic config reloading works
When Logstash detects a change in a config file, it stops the current pipeline by stopping
all inputs, and it attempts to create a new pipeline that uses the updated configuration.