# New elasticsearch node does not run enrichments **URL:** \ **Category:** Elasticsearch\ **Tags:** docker, ingest-pipeline\ **Created:** [April 21, 2023, 1:26pm UTC](https://discuss.elastic.co/t/new-elasticsearch-node-does-not-run-enrichments/330523 "2023-04-21T13:26:06Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [April 21, 2023, 2:02pm UTC](https://discuss.elastic.co/t/new-elasticsearch-node-does-not-run-enrichments/330523/4 "2023-04-21T14:02:50Z")
> [@FKarraz](#): > > If the corresponding shard is allocated in node02 (elasticsearch02), shouldn't node01 forward the indexing request to node02? I'm not sure about the internals, but the indexing request to write on the shard is done after the ingest process, so the data is processed by the ingest pipeline, which will run the enrich processors and after that they will be written on the specific shards. > [@FKarraz](#): > > And one more question, suppose I restart the node02 container exposing port 9200. In the elasticsearch02 configuration I do not map the data volumes to the host. If I restart the service, the data of the shards allocated in node02 should not be lost, right? > (All this in a scenario where, due to limited resources, I only have primaries shards configured). No, if you do not have a persistent volume for the node02, the data **will be lost** if you restart it, every data node needs to have persistent volume. Do not restart your node02 if you have data on it and do not have a persistent volume mounted, you need first to remove the data from the node, remove the node and add a persistent volume for it to work. --- _[View the full topic](https://discuss.elastic.co/t/new-elasticsearch-node-does-not-run-enrichments/330523)._