as the topic, i send the kill -SIGHUP xxx to the logstash ,but the config still same.
version 8.11.3
linux: Linux CS-gxxt-tyzj-03 4.19.90-52.22.v2207.ky10.aarch64 #1 SMP Tue Mar 14 11:52:45 CST 2023 aarch64 aarch64 aarch64 GNU/Linux
as the topic, i send the kill -SIGHUP xxx to the logstash ,but the config still same.
version 8.11.3
linux: Linux CS-gxxt-tyzj-03 4.19.90-52.22.v2207.ky10.aarch64 #1 SMP Tue Mar 14 11:52:45 CST 2023 aarch64 aarch64 aarch64 GNU/Linux
Hi,
The kill -SIGHUP
command is used to reload the configuration in some applications, but in the case of Logstash, this is not the correct way to reload the configuration.
If you want to manually reload the configuration, you can send a SIGHUP
signal to the Logstash process, but this requires the --config.reload.automatic
option to be enabled.
bin/logstash --config.reload.automatic
Regards
Just to add that this only works when you run Logstash from the command line, if Logstash is running as a service, which is way more common, this setting needs to be added to logstash.yml
and the service needs to be restarted once.
config.reload.automatic: true
got it ,thks
thks.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.