You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@usergrid.apache.org by "John D. Ament (JIRA)" <ji...@apache.org> on 2015/02/22 21:29:11 UTC

[jira] [Commented] (USERGRID-408) Create a shard balance system

    [ https://issues.apache.org/jira/browse/USERGRID-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332341#comment-14332341 ] 

John D. Ament commented on USERGRID-408:
----------------------------------------

Hey Todd

I read through your forum post, and coming out of the elasticsearch battlegrounds, I think you might be confusing shards and replicas.

The shard is a logical separation of indexed data across an index.  If your index is lets say 1gb in size, that might be too big to process, so splitting the index across 3 333MB shards is an option to avoid loading the whole thing into memory at once.

A replica is how many copies of that data you want around.  The default replica count is 2, depending on cluster size.

I think in the structure you're describing, you want 1 shard and 6 replicas, not 6 shards.

> Create a shard balance system
> -----------------------------
>
>                 Key: USERGRID-408
>                 URL: https://issues.apache.org/jira/browse/USERGRID-408
>             Project: Usergrid
>          Issue Type: Story
>            Reporter: Todd Nine
>
> Currently when an index is created, it should have the same number of shards as ES nodes with replica's.  Since we sometimes do not allocate replicas, we need to ensure that primary shards are evenly distributed among our nodes.  If this can't be fixed with ES settings, we will need to create an api function that evenly balances primary and replica shards across the cluster per index.  See this forum post.
> https://groups.google.com/forum/#!topic/elasticsearch/9Hb5CJJ5Vj0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)