# How to share custom Elasticsearch plugin specific data across nodes

**URL:** <https://discuss.elastic.co/t/how-to-share-custom-elasticsearch-plugin-specific-data-across-nodes/225654>\
**Category:** Elasticsearch\
**Created:** [March 30, 2020, 10:23am UTC](https://discuss.elastic.co/t/how-to-share-custom-elasticsearch-plugin-specific-data-across-nodes/225654 "2020-03-30T10:23:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sbrisi](https://avatars.discourse-cdn.com/v4/letter/s/b38774/32.png) [@sbrisi](https://discuss.elastic.co/u/sbrisi)\
**Post date:** [March 30, 2020, 10:23am UTC](https://discuss.elastic.co/t/how-to-share-custom-elasticsearch-plugin-specific-data-across-nodes/225654/1 "2020-03-30T10:23:47Z")

</div>

How to share custom Elasticsearch plugin-specific data across nodes. Our plugin uses the temp filesystem to store data which would be re-used, how do I share this across multiple nodes in an Elasticsearch cluster without using the file system. What persistent operations are available to support this, should we use a shared filesystem or relational database based persistence. What are the best practices here?

We would want to backup and restore this custom plugin-specific data if we migrate or upgrade our Elasticsearch clusters

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 27, 2020, 10:25am UTC](https://discuss.elastic.co/t/how-to-share-custom-elasticsearch-plugin-specific-data-across-nodes/225654/2 "2020-04-27T10:25:43Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
