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
>
> 1) Start all master nodes
> 2) "cluster.routing.allocation.enable" : "none"
> 3) Start all data nodes
> 4) 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"
> }
> }
> }
> }
>
> }
>
> Cluster status is yellow
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/8a04bad1-6985-46ea-8f04-bec0c86c65bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
