# Please provide suggestions on this

**URL:** <https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923>\
**Category:** Elasticsearch\
**Created:** [September 30, 2016, 1:42pm UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923 "2016-09-30T13:42:13Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![banu](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@banu](https://discuss.elastic.co/u/banu)\
**Post date:** [September 30, 2016, 1:42pm UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/1 "2016-09-30T13:42:13Z")

</div>

```
     how data will be distributed when we have single index(1 shard and 1 replica) stored into 2 nodes server. Primary will be stored into one node and replica will be stored in to another node. What will happen when disk space reached its max capacity and adding new node to avoid failure in this scenario? Will new data for the index be loaded into newly added node or it cannot be loaded? If it can be loaded in to new node , will it not impact relevance score? 

```

 Can we move one index to other node if we have 2 index with above scenarios. ?  
 During initial data load if we have 10 indexes, is there anywhere we can control to assign primary index in any specific node among multiple nodes. ?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 1, 2016, 11:32am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/2 "2016-10-01T11:32:59Z")

</div>

Please format your question a little better, you have a single massive line that people need to scroll through just to see what you are asking.

---

<div class="post-metadata">

**Author:** ![banu](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@banu](https://discuss.elastic.co/u/banu)\
**Post date:** [October 3, 2016, 5:27am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/3 "2016-10-03T05:27:49Z")

</div>

how data will be distributed when we have single index(1 shard and 1 replica) stored into 2 nodes server.  
Primary will be stored into one node and replica will be stored in to another node.  
What will happen when disk space reached its max capacity and adding new node to avoid failure in this scenario? Will new data for the index be loaded into newly added node or it cannot be loaded? If it can be loaded in to new node , will it not impact relevance score?  
[/quote]

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 3, 2016, 5:55am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/4 "2016-10-03T05:55:07Z")

</div>

> [@banu](#):
>
> Primary will be stored into one node and replica will be stored in to another node.

Yes.

> [@banu](#):
>
> What will happen when disk space reached its max capacity and adding new node to avoid failure in this scenario?

Adding another node after a node gets to 100% disk use is no good. Do it before.

---

<div class="post-metadata">

**Author:** ![banu](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@banu](https://discuss.elastic.co/u/banu)\
**Post date:** [October 3, 2016, 6:15am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/5 "2016-10-03T06:15:22Z")

</div>

will it not impact relevance score?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 3, 2016, 6:18am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/6 "2016-10-03T06:18:16Z")

</div>

Scoring is calculated against docs in the same shard. So no.

---

<div class="post-metadata">

**Author:** ![banu](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@banu](https://discuss.elastic.co/u/banu)\
**Post date:** [October 3, 2016, 6:20am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/7 "2016-10-03T06:20:36Z")

</div>

Can we move one index to other node if we have 2 index with above scenarios. ?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 3, 2016, 6:23am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/8 "2016-10-03T06:23:01Z")

</div>

Maybe, you'd need to test really because ES doesn't generally like full disks.

---

<div class="post-metadata">

**Author:** ![banu](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@banu](https://discuss.elastic.co/u/banu)\
**Post date:** [October 3, 2016, 6:46am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/9 "2016-10-03T06:46:50Z")

</div>

During initial data load if we have 10 indexes, is there anywhere we can control to assign primary index in any specific node among multiple nodes. ?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 3, 2016, 6:47am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/10 "2016-10-03T06:47:41Z")

</div>

Nope. It shouldn't matter.

---

<div class="post-metadata">

**Author:** ![banu](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@banu](https://discuss.elastic.co/u/banu)\
**Post date:** [October 3, 2016, 7:02am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/11 "2016-10-03T07:02:52Z")

</div>

then how to handle when max disk space reached?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 3, 2016, 7:04am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/12 "2016-10-03T07:04:12Z")

</div>

Prevention is better than cure in this case.

---

<div class="post-metadata">

**Author:** ![banu](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@banu](https://discuss.elastic.co/u/banu)\
**Post date:** [October 3, 2016, 7:50am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/13 "2016-10-03T07:50:00Z")

</div>

Hey mark i need more detailed description on this scenario i have 1shard 1 replica and 2nodes if i am indexing millions of documents when the disk reaches the max capacity ?whether we can increase node size or shards size which is recommended to increase ?

---

<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:** [October 3, 2016, 8:03am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/14 "2016-10-03T08:03:39Z")

</div>

If you have a single index with just 1 shard and 1 replica, there is little you can do around redistributing data if the disk gets full as shards can not be split. You can however provision nodes with more disk space and move the shard over there in order to scale up, but you will not be able to scale horizontally. If you however had more than 1 shard, you could add nodes to the cluster and scale out horizontally as Elasticsearch would relocate a portion of the shards on the node and free up space.

---

<div class="post-metadata">

**Author:** ![banu](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@banu](https://discuss.elastic.co/u/banu)\
**Post date:** [October 3, 2016, 9:16am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/15 "2016-10-03T09:16:55Z")

</div>

Thanks christian for your suggestion i do have another query During initial data load if we have 10 indexes, is there anywhere we can control to assign primary index in any specific node among multiple nodes.

---

<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:** [October 3, 2016, 9:28am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/16 "2016-10-03T09:28:59Z")

</div>

I assume you are referring to primary shards as there are no primary indices, and if this is the case the answer is no, as this is not possible. Primaries and replicas however do the same amount of work, so you should not need to be concerned with this.

---

<div class="post-metadata">

**Author:** ![banu](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@banu](https://discuss.elastic.co/u/banu)\
**Post date:** [October 3, 2016, 9:43am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/17 "2016-10-03T09:43:58Z")

</div>

if i have 5 nodes and 5th name is "testnode" and the index name is "testindex" is it possible to assign the "testindex" to "testnode" ?

---

<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:** [October 3, 2016, 9:55am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/18 "2016-10-03T09:55:56Z")

</div>

Yes, that should be possible through [shard allocation awareness](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/allocation-awareness.html).

---

<div class="post-metadata">

**Author:** ![banu](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@banu](https://discuss.elastic.co/u/banu)\
**Post date:** [October 3, 2016, 10:07am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/19 "2016-10-03T10:07:29Z")

</div>

Thanks for your suggestion christian 🙂

---

<div class="post-metadata">

**Author:** ![banu](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@banu](https://discuss.elastic.co/u/banu)\
**Post date:** [October 3, 2016, 11:09am UTC](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923/20 "2016-10-03T11:09:33Z")

</div>

If we have 2 shard in one node then the data will be splited in each shard

[Next page](https://discuss.elastic.co/t/please-provide-suggestions-on-this/61923.md?page=2)
