# Elastic Search data is not being stored in one of the three PVCs
**URL:** https://discuss.elastic.co/t/elastic-search-data-is-not-being-stored-in-one-of-the-three-pvcs/354872
**Category:** Elasticsearch
**Created:** [March 6, 2024, 7:17pm UTC](https://discuss.elastic.co/t/elastic-search-data-is-not-being-stored-in-one-of-the-three-pvcs/354872 "2024-03-06T19:17:34Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Siva\_Vignesh\_K](https://discuss.elastic.co/u/Siva_Vignesh_K)
#### Post date: [March 6, 2024, 7:17pm UTC](https://discuss.elastic.co/t/elastic-search-data-is-not-being-stored-in-one-of-the-three-pvcs/354872/1 "2024-03-06T19:17:34Z")
Using Helm Chart, I have deployed three replicas of elasticsearch in a Kubernetes cluster. I've noticed that data is only being stored in the two PVCs. My storage is filling up quickly since the third one is not receiving any data. I don't know of any workarounds for this problem. Could you please share your insights? Thank You
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [March 6, 2024, 8:08pm UTC](https://discuss.elastic.co/t/elastic-search-data-is-not-being-stored-in-one-of-the-three-pvcs/354872/2 "2024-03-06T20:08:03Z")
Do you by any chance have one index with one primary and one replica shard that is very large? If not, can you show the output of the cat shards API?
---
### Author:  [@Siva\_Vignesh\_K](https://discuss.elastic.co/u/Siva_Vignesh_K)
#### Post date: [March 6, 2024, 9:44pm UTC](https://discuss.elastic.co/t/elastic-search-data-is-not-being-stored-in-one-of-the-three-pvcs/354872/3 "2024-03-06T21:44:20Z")
Thanks for the reply.
Here, 'aws-kensho' is the index that will receive more data.
My observation is that 'aws-kensho' has only two replicas elasticsearch-master-0 and elasticsearch-master-1.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [March 7, 2024, 6:19am UTC](https://discuss.elastic.co/t/elastic-search-data-is-not-being-stored-in-one-of-the-three-pvcs/354872/4 "2024-03-07T06:19:36Z")
Elasticsearch distributes data across the cluster in units of shards. As you have a single index with 2 shards (one primary and one replica) that is much larger than all the others combined these can ever only be allocated to 2 nodes as Elasticsearch will not split these up. This is why you data will never be balanced across your cluster. As the size of the shards is very large I would recommend [increasing the number of primary shards by splitting it](https://www.elastic.co/guide/en/elasticsearch/reference/8.12/indices-split-index.html), but be aware that this will require a lot of extra storage, at least temporarily. If you had a higher number of primary shards Elasticsearch would be able to more evenly distribute data.
If the data is immutable and expected to continue growing over time I would recommend using [a data stream](https://www.elastic.co/guide/en/elasticsearch/reference/8.12/data-streams.html) instead of a single index.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 4, 2024, 6:19am UTC](https://discuss.elastic.co/t/elastic-search-data-is-not-being-stored-in-one-of-the-three-pvcs/354872/5 "2024-04-04T06:19:55Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.