Thanks. Is there a size based allocation. What seems to be is that we have
allocation based on number of primaries, per index, per node, etc. Is there
a size factor that comes into play like, say if the routing is not even
function, and shards on one node are more heavily loaded than another?
Thanks,
Sandeep
On Thursday, 21 August 2014 12:44:56 UTC+5:30, Jörg Prante wrote:
There is a formula ES uses by default to find if nodes get unbalanced
regarding the shards. See
There is disk-based allocation. It does not take shard volume into account.
It is not always a good idea to use total shard volume per node as a
measurement across indices, consider heavy bulk indexing with steep volume
changes, but the remaining disk space.
If you mean search load by "heavily loaded", I suggest to just add replica,
maybe auto expand replica, so each node holds every shard as a copy, for
best load balancing.
Thanks. Is there a size based allocation. What seems to be is that we have
allocation based on number of primaries, per index, per node, etc. Is there
a size factor that comes into play like, say if the routing is not even
function, and shards on one node are more heavily loaded than another?
Thanks,
Sandeep
On Thursday, 21 August 2014 12:44:56 UTC+5:30, Jörg Prante wrote:
There is a formula ES uses by default to find if nodes get unbalanced
regarding the shards. See
On Thu, Aug 21, 2014 at 8:26 AM, 'Sandeep Ramesh Khanzode' via
elasticsearch elasti...@googlegroups.com wrote:
Hi,
What can be the possible causes when Elasticsearch will automatically
reallocate a shard from node in the cluster to another node?
One can be obviously when you add a new node.
What are the automatic triggers, like continuously indexing new data or
something? What is the policy for this?
Thanks,
Sandeep
--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.com.
Is it possible that once the shards have been allocated by this formula or
the policies, they will ever change again.
I mean, if we have 3 indices on a two node cluster with 10 shards each. Now
I add another index with 10 shards, will the EXISTING indices' shards be
reallocated? Or is reallocation only for new shards?
On Thursday, 21 August 2014 13:49:54 UTC+5:30, Jörg Prante wrote:
There is disk-based allocation. It does not take shard volume into
account. It is not always a good idea to use total shard volume per node as
a measurement across indices, consider heavy bulk indexing with steep
volume changes, but the remaining disk space.
If you mean search load by "heavily loaded", I suggest to just add
replica, maybe auto expand replica, so each node holds every shard as a
copy, for best load balancing.
Jörg
On Thu, Aug 21, 2014 at 9:57 AM, 'Sandeep Ramesh Khanzode' via
elasticsearch <elasti...@googlegroups.com <javascript:>> wrote:
Hi Jorg,
Thanks. Is there a size based allocation. What seems to be is that we
have allocation based on number of primaries, per index, per node, etc. Is
there a size factor that comes into play like, say if the routing is not
even function, and shards on one node are more heavily loaded than another?
Thanks,
Sandeep
On Thursday, 21 August 2014 12:44:56 UTC+5:30, Jörg Prante wrote:
There is a formula ES uses by default to find if nodes get unbalanced
regarding the shards. See
On Thu, Aug 21, 2014 at 8:26 AM, 'Sandeep Ramesh Khanzode' via
elasticsearch elasti...@googlegroups.com wrote:
Hi,
What can be the possible causes when Elasticsearch will automatically
reallocate a shard from node in the cluster to another node?
One can be obviously when you add a new node.
What are the automatic triggers, like continuously indexing new data or
something? What is the policy for this?
Thanks,
Sandeep
--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.com.
Is it possible that once the shards have been allocated by this formula or
the policies, they will ever change again.
I mean, if we have 3 indices on a two node cluster with 10 shards each.
Now I add another index with 10 shards, will the EXISTING indices' shards
be reallocated? Or is reallocation only for new shards?
On Thursday, 21 August 2014 13:49:54 UTC+5:30, Jörg Prante wrote:
There is disk-based allocation. It does not take shard volume into
account. It is not always a good idea to use total shard volume per node as
a measurement across indices, consider heavy bulk indexing with steep
volume changes, but the remaining disk space.
If you mean search load by "heavily loaded", I suggest to just add
replica, maybe auto expand replica, so each node holds every shard as a
copy, for best load balancing.
Jörg
On Thu, Aug 21, 2014 at 9:57 AM, 'Sandeep Ramesh Khanzode' via
elasticsearch elasti...@googlegroups.com wrote:
Hi Jorg,
Thanks. Is there a size based allocation. What seems to be is that we
have allocation based on number of primaries, per index, per node, etc. Is
there a size factor that comes into play like, say if the routing is not
even function, and shards on one node are more heavily loaded than another?
Thanks,
Sandeep
On Thursday, 21 August 2014 12:44:56 UTC+5:30, Jörg Prante wrote:
There is a formula ES uses by default to find if nodes get unbalanced
regarding the shards. See
On Thu, Aug 21, 2014 at 8:26 AM, 'Sandeep Ramesh Khanzode' via
elasticsearch elasti...@googlegroups.com wrote:
Hi,
What can be the possible causes when Elasticsearch will automatically
reallocate a shard from node in the cluster to another node?
One can be obviously when you add a new node.
What are the automatic triggers, like continuously indexing new data
or something? What is the policy for this?
Thanks,
Sandeep
--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.com.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.