Hi,
i have one ELS 1.1.2 cluster with 7 nodes.
800GB data.
When i shutdown a node for various reasons, ELS automatically rebalance the
missing shard on the other node.
To prevent this, I tried this (specified in the official doc) :
"transient" : {
"cluster.routing.allocation.enable" : "none" }
ans then i issue a node shtudown.
Effectively, the relevant shards are now unassigned and ELS don't try to
reallocate them.
But when i restart the node, they still remain as "unassigned".
And then when i set back :
"transient" : {
"cluster.routing.allocation.enable" : "all" }
=> ELS reallocate unassigned shard to ALL nodes instead of the restarted
node.
Hi,
i have one ELS 1.1.2 cluster with 7 nodes.
800GB data.
When i shutdown a node for various reasons, ELS automatically rebalance
the missing shard on the other node.
To prevent this, I tried this (specified in the official doc) :
"transient" : {
"cluster.routing.allocation.enable" : "none" }
ans then i issue a node shtudown.
Effectively, the relevant shards are now unassigned and ELS don't try to
reallocate them.
But when i restart the node, they still remain as "unassigned".
And then when i set back :
"transient" : {
"cluster.routing.allocation.enable" : "all" }
=> ELS reallocate unassigned shard to ALL nodes instead of the restarted
node.
You've followed the right procedure. The problem is that Elasticsearch
doesn't always restore the shards back on the node that they came from. If
the restarted shard and the current master shard have diverge at all it'll
have to sync files somewhere to make sure that the restarted shard gets
all the changes. Since shards diverge all the time even if there aren't
updates while the node is down you can expect this.
Speeding this process up has been an open issue for many many months.
Hi,
i have one ELS 1.1.2 cluster with 7 nodes.
800GB data.
When i shutdown a node for various reasons, ELS automatically rebalance
the missing shard on the other node.
To prevent this, I tried this (specified in the official doc) :
"transient" : {
"cluster.routing.allocation.enable" : "none" }
ans then i issue a node shtudown.
Effectively, the relevant shards are now unassigned and ELS don't try to
reallocate them.
But when i restart the node, they still remain as "unassigned".
And then when i set back :
"transient" : {
"cluster.routing.allocation.enable" : "all" }
=> ELS reallocate unassigned shard to ALL nodes instead of the restarted
node.
ok thank for your explanation.
It's a major concern as ELS is scalabe and when a node goes down, we have a
rebalancing process which can take lot ot time.
i find it strange that this point has not been adressed long time ago
I think with a big cluster (>100 nodes) then the cluster is permanently
rebalacing (consuming network and performance) as nodes crash frequently.
Is it the same if i put the index in read only mode ?
Le lundi 10 novembre 2014 17:58:19 UTC+1, Nikolas Everett a écrit :
You've followed the right procedure. The problem is that Elasticsearch
doesn't always restore the shards back on the node that they came from. If
the restarted shard and the current master shard have diverge at all it'll
have to sync files somewhere to make sure that the restarted shard gets
all the changes. Since shards diverge all the time even if there aren't
updates while the node is down you can expect this.
Speeding this process up has been an open issue for many many months.
Reallocation to all nodes is the expected behavior.
Jörg
On Mon, Nov 10, 2014 at 3:55 PM, lagarutte via elasticsearch < elasti...@googlegroups.com <javascript:>> wrote:
Hi,
i have one ELS 1.1.2 cluster with 7 nodes.
800GB data.
When i shutdown a node for various reasons, ELS automatically rebalance
the missing shard on the other node.
To prevent this, I tried this (specified in the official doc) :
"transient" : {
"cluster.routing.allocation.enable" : "none" }
ans then i issue a node shtudown.
Effectively, the relevant shards are now unassigned and ELS don't try to
reallocate them.
But when i restart the node, they still remain as "unassigned".
And then when i set back :
"transient" : {
"cluster.routing.allocation.enable" : "all" }
=> ELS reallocate unassigned shard to ALL nodes instead of the
restarted node.
ok thank for your explanation.
It's a major concern as ELS is scalabe and when a node goes down, we have
a rebalancing process which can take lot ot time.
i find it strange that this point has not been adressed long time ago
I think with a big cluster (>100 nodes) then the cluster is permanently
rebalacing (consuming network and performance) as nodes crash frequently.
Is it the same if i put the index in read only mode ?
Le lundi 10 novembre 2014 17:58:19 UTC+1, Nikolas Everett a écrit :
You've followed the right procedure. The problem is that Elasticsearch
doesn't always restore the shards back on the node that they came from. If
the restarted shard and the current master shard have diverge at all it'll
have to sync files somewhere to make sure that the restarted shard gets
all the changes. Since shards diverge all the time even if there aren't
updates while the node is down you can expect this.
Speeding this process up has been an open issue for many many months.
Hi,
i have one ELS 1.1.2 cluster with 7 nodes.
800GB data.
When i shutdown a node for various reasons, ELS automatically rebalance
the missing shard on the other node.
To prevent this, I tried this (specified in the official doc) :
"transient" : {
"cluster.routing.allocation.enable" : "none" }
ans then i issue a node shtudown.
Effectively, the relevant shards are now unassigned and ELS don't try
to reallocate them.
But when i restart the node, they still remain as "unassigned".
And then when i set back :
"transient" : {
"cluster.routing.allocation.enable" : "all" }
=> ELS reallocate unassigned shard to ALL nodes instead of the
restarted node.
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.