# Data path already locked by another beat ,how to configure path.data in running on kubernetes filebeat-kubernetes.yaml

**URL:** <https://discuss.elastic.co/t/data-path-already-locked-by-another-beat-how-to-configure-path-data-in-running-on-kubernetes-filebeat-kubernetes-yaml/260036>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 3, 2021, 11:10am UTC](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat-how-to-configure-path-data-in-running-on-kubernetes-filebeat-kubernetes-yaml/260036 "2021-01-03T11:10:43Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![umen](https://avatars.discourse-cdn.com/v4/letter/u/ec9cab/32.png) [@umen](https://discuss.elastic.co/u/umen)\
**Post date:** [January 7, 2021, 3:25pm UTC](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat-how-to-configure-path-data-in-running-on-kubernetes-filebeat-kubernetes-yaml/260036/7 "2021-01-07T15:25:57Z")

</div>

@ChrsMark  
Well everything worked fine ( other problems are raised )  
After i changed the configuration to this: ( see last comment )

> [@Filebeat not collection logs of elastic pods](https://discuss.elastic.co/t/filebeat-not-collection-logs-of-elastic-pods/259719/4):
>
> Hi @umen any update on your side regarding that issue?

but the error in the log is still the same very storage...  
i don't know where it Will bite me in later on...

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/3/332c9f3136dbd841603bac6a017bea6d9e5e95f7.png)

---

_[View the full topic](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat-how-to-configure-path-data-in-running-on-kubernetes-filebeat-kubernetes-yaml/260036)._