# How does the elasticsearch expand capacity and shrink capacity？

**URL:** <https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396>\
**Category:** Elasticsearch\
**Created:** [September 5, 2017, 9:39am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396 "2017-09-05T09:39:13Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![saliormoon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/saliormoon/32/21499_2.png) [@saliormoon](https://discuss.elastic.co/u/saliormoon)\
**Post date:** [September 5, 2017, 9:39am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/1 "2017-09-05T09:39:14Z")

</div>

elasticsearch version: 5.5.2  
OS: Linux  
A cluster of 3 nodes.

How does elasticsearch reduce capacity and scale out capacity? Is there any operation command?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 5, 2017, 9:44am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/2 "2017-09-05T09:44:45Z")

</div>

What do you mean by expanding and shrinking capacity?

---

<div class="post-metadata">

**Author:** ![saliormoon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/saliormoon/32/21499_2.png) [@saliormoon](https://discuss.elastic.co/u/saliormoon)\
**Post date:** [September 5, 2017, 10:06am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/3 "2017-09-05T10:06:50Z")

</div>

Sorry， I mean how elasticsearch reduce capacity and scale out capacity.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 5, 2017, 10:12am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/4 "2017-09-05T10:12:40Z")

</div>

What type of capacity? Storage, nodes, heap, RAM, CPU?

---

<div class="post-metadata">

**Author:** ![saliormoon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/saliormoon/32/21499_2.png) [@saliormoon](https://discuss.elastic.co/u/saliormoon)\
**Post date:** [September 5, 2017, 10:15am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/5 "2017-09-05T10:15:53Z")

</div>

Yes, it is storage. Now I put large amount of data in the index, but the primary shards can't store any more, how to solve this problem?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 5, 2017, 10:17am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/6 "2017-09-05T10:17:36Z")

</div>

What is your use case? How many indices and shards do you have? How many documents in total? How large are the indices and shards?

---

<div class="post-metadata">

**Author:** ![saliormoon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/saliormoon/32/21499_2.png) [@saliormoon](https://discuss.elastic.co/u/saliormoon)\
**Post date:** [September 5, 2017, 10:26am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/7 "2017-09-05T10:26:10Z")

</div>

Yeah, thanks. I put 10TB data into one index, and there are 3 primary shards and 6 replica shards, if I want to store more data, how to scale out the storage of elasticsearch.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 5, 2017, 10:28am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/8 "2017-09-05T10:28:17Z")

</div>

What type of data do you have? What is the use case? I assume the PB is a typo? Should it be GB or TB?

---

<div class="post-metadata">

**Author:** ![saliormoon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/saliormoon/32/21499_2.png) [@saliormoon](https://discuss.elastic.co/u/saliormoon)\
**Post date:** [September 5, 2017, 10:37am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/9 "2017-09-05T10:37:43Z")

</div>

Yeah, the unit is PB. Because the number of primary shards can't be modified once created, then how do we scale out their storage later?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 5, 2017, 10:46am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/10 "2017-09-05T10:46:33Z")

</div>

It looks like you corrected it to TB. What is the use case? What type of data do you have? The reason I am asking this is that it impacts how you best manage your data.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 5, 2017, 10:50am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/11 "2017-09-05T10:50:20Z")

</div>

I would recommend you read this section from 'Elasticsearch: the definitive guide' around [designing for scale](https://www.elastic.co/guide/en/elasticsearch/guide/current/scale.html).

---

<div class="post-metadata">

**Author:** ![saliormoon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/saliormoon/32/21499_2.png) [@saliormoon](https://discuss.elastic.co/u/saliormoon)\
**Post date:** [September 5, 2017, 10:52am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/12 "2017-09-05T10:52:38Z")

</div>

Sorry, I don't have particular type of data now, I just assumpt that.

---

<div class="post-metadata">

**Author:** ![saliormoon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/saliormoon/32/21499_2.png) [@saliormoon](https://discuss.elastic.co/u/saliormoon)\
**Post date:** [September 5, 2017, 10:58am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/13 "2017-09-05T10:58:22Z")

</div>

Thanks, but there aren't many operations guides in the page. I'm sorry that I still have no idea how to do.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 5, 2017, 10:59am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/14 "2017-09-05T10:59:40Z")

</div>

You define your indexing and sharing strategy based on what type of data you have, which is described in the documentation I linked to. Elasticsearch will use the storage it has available and once you reach the limit of the nodes in the cluster, you usually scale up/and or out, at which point Elasticsearch will redistribute the data.

Once you have more details we might be able to provide better and more detailed guidance.

---

<div class="post-metadata">

**Author:** ![saliormoon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/saliormoon/32/21499_2.png) [@saliormoon](https://discuss.elastic.co/u/saliormoon)\
**Post date:** [September 5, 2017, 11:10am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/15 "2017-09-05T11:10:48Z")

</div>

Thanks, we really looking forward to your more detailed guidance. And could you explain a lit more detail about how Elasticsearch redistribute the data?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 5, 2017, 11:17am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/16 "2017-09-05T11:17:26Z")

</div>

Please read the full chapter I linked earlier. You may also find [this guide](https://www.elastic.co/guide/en/elasticsearch/guide/current/administration.html) useful.

Without details around your use-case or data I am afraid I can not provide any more detailed guidance.

---

<div class="post-metadata">

**Author:** ![saliormoon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/saliormoon/32/21499_2.png) [@saliormoon](https://discuss.elastic.co/u/saliormoon)\
**Post date:** [September 6, 2017, 2:50am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/17 "2017-09-06T02:50:33Z")

</div>

Ok, thanks a lot.

---

<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:** [October 4, 2017, 2:50am UTC](https://discuss.elastic.co/t/how-does-the-elasticsearch-expand-capacity-and-shrink-capacity/99396/18 "2017-10-04T02:50:35Z")

</div>

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