We are using ES version 1.4.1. We have hourly index with 50 shards per
index and replication is 1 . We restarted our cluster after the some
maintenance we had from system side. No we don't have any disk failures.
After the restart, i see all primary shards are assigned but all replicas
are unassigned?
After cluster shutdown, these are the steps we followed to do the restart
Start all master nodes
"cluster.routing.allocation.enable" : "none"
Start all data nodes
After all nodes joined the cluster we did
cluster.routing.allocation.enable" : "all"
for cluster setting this it shows.
{
persistent: { },
transient:
{
cluster:
{
routing:
{
allocation:
{
enable: "all"
}
}
}
}
}
Pending tasks queue is empty. Cluster status is yellow
One correction. Pending tasks queue is not empty and it shows one task.
18596 56.1m URGENT reroute_after_cluster_update_settings. I think this is *cluster.routing.allocation.*enable" : "all" we executed after all nodes joined the cluster. Setting got updated on all the nodes. But why it is still in the queue from last 56 m?
On Friday, January 23, 2015 at 4:48:10 PM UTC-8, Darsh wrote:
We are using ES version 1.4.1. We have hourly index with 50 shards per
index and replication is 1 . We restarted our cluster after the some
maintenance we had from system side. No we don't have any disk failures.
After the restart, i see all primary shards are assigned but all replicas
are unassigned?
After cluster shutdown, these are the steps we followed to do the restart
Start all master nodes
"cluster.routing.allocation.enable" : "none"
Start all data nodes
After all nodes joined the cluster we did
cluster.routing.allocation.enable" : "all"
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.