My questions always seem to go un-answered. I guess I need to ask why my
term query doesn't work instead of the more esoteric inner workings. 
In the end, waiting for relocating shards might not be the answer since
newly added replicas are in the recovering state, not relocating. Does
anybody have a workflow that waits until the cluster is green after
increasing the number of replicas after a bulk index? Wait for green does
not work since the cluster is green for a bit before finally turning to
yellow. My current process is to wait for yellow, then to wait for green,
which is kludgy and does not always work.
Cheers,
Ivan
On Tue, Jan 29, 2013 at 12:51 PM, Ivan Brusic ivan@brusic.com wrote:
The ClusterHealthRequest allows one to wait for a specified number of
relocating shards. Would it be possible to extend the class to wait for all
relocating shards? Currently, I need to make one request to get the number
of relocating shards and then another request to wait for those shards to
finish relocating. Eliminating the need for the first request would be
optimal.My use case is to move an alias and ever administrative tasks once a full
index has been rolled out after the number of replicas has been increased
from 0 (set to zero to speed up a full re-index).Ivan
--
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.