# Data path already locked by another beat

**URL:** <https://discuss.elastic.co/t/data-path-already-locked-by-another-beat/219852>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 18, 2020, 7:11pm UTC](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat/219852 "2020-02-18T19:11:38Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\
**Post date:** [February 19, 2020, 3:29pm UTC](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat/219852/4 "2020-02-19T15:29:55Z")

</div>

Hmmm, you're right that this [important breaking change](https://github.com/elastic/beats/pull/14069) is not in the release notes or breaking changes doc for 7.6.0. I'm terribly sorry about that and am [working](https://github.com/elastic/beats/pull/16424) 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}/`.

Shaunak

---

_[View the full topic](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat/219852)._