Control the order of shards recovery on node re-start

Elastic Stack Elasticsearch
1

Hi All,

We are maintaining 200 shards per node and each shard has 50 to 100 GB
of data. We are creating a new index for each day. Due to large number of
shards and large shard size, the restart of node is taking very high time.

Is it possible to control the order of recovery of shards, so that the
shards of current index will recover first, then the shards of previous day
index and so on?

Regards,
Ankit Jain

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

2

I'm not sure what's the best way to do this but as a workaround, you
could close the indices before doing a restart and then open them in
the order you want the indices to be recovered.

On Mon, Oct 14, 2013 at 10:43 PM, Ankit Jain ankitjaincs06@gmail.com wrote:

Hi All,

We are maintaining 200 shards per node and each shard has 50 to 100 GB of
data. We are creating a new index for each day. Due to large number of
shards and large shard size, the restart of node is taking very high time.

Is it possible to control the order of recovery of shards, so that the
shards of current index will recover first, then the shards of previous day
index and so on?

Regards,
Ankit Jain

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Regards,
Abhijeet Rastogi (shadyabhi)

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

3

Hi Abhijeet,

Thanks for response.

A workaround suggested by you is good but we would require a solution which
can also work in case of node craches.
Also, we don't want to close whole indices in case of restart of one
node that server only few shards.

Regards,
Ankit Jain

On Wednesday, 16 October 2013 16:46:11 UTC+5:30, Abhijeet Rastogi wrote:

I'm not sure what's the best way to do this but as a workaround, you
could close the indices before doing a restart and then open them in
the order you want the indices to be recovered.

Elasticsearch Platform — Find real-time answers at scale | Elastic

On Mon, Oct 14, 2013 at 10:43 PM, Ankit Jain <ankitj...@gmail.com<javascript:>>
wrote:

Hi All,

We are maintaining 200 shards per node and each shard has 50 to 100 GB
of
data. We are creating a new index for each day. Due to large number of
shards and large shard size, the restart of node is taking very high
time.

Is it possible to control the order of recovery of shards, so that the
shards of current index will recover first, then the shards of previous
day
index and so on?

Regards,
Ankit Jain

--
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 <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.

--
Regards,
Abhijeet Rastogi (shadyabhi)

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.