after upgrading from 7.5.1 to 7.6.0 my filebeat breaks with error data path already locked by another beat
i have two instances of filebeat running for a very long time, one reading a specific set of files and sending to logstash, and the other one reading another set of files and sending to elasticsearch.
could not find this breaking change on the docs below.
Hmmm, you're right that this important breaking change is not in the release notes or breaking changes doc for 7.6.0. I'm terribly sorry about that and am working to get it documented ASAP!
As for fixing your setup to account for this change, please edit both your Filebeat configuration files and add a path.data setting. Make sure to set it's values to unique directory locations. Then you should set filebeat.registry.path to start with ${path.data}/.
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.