Hey,
Monitor: it is all in the cluster state. Use a plugin like head or
paramedic to monitor it. If you play around with 1.0.0 beta, check out the
Cat API, which is a neat commandline interface to find out, what happens in
your cluster.
Control: You can control relocation. You can enable/disable it, set up
rules which nodes should hold which shards or if shards should be moved
around based on disk space allocation (allocation, awareness, forced
awareness).
Practices: You can throttle the amount of concurrent relocations (per
node), you can throttle its throughput to make sure that daily business
like searching and indexing still work as in lines with your SLA.
Hope this helps is there any specific hidden concrete question? 
--Alex
On Wed, Dec 18, 2013 at 10:28 PM, Mohit Anchlia mohitanchlia@gmail.comwrote:
What's the best way to monitor shard relocation that occurrs when one add
new nodes?
Is there a way to control the relocation and do it manually with few
shards at a time?
What are the best practices for cluster that is contantly received high
volume traffic?
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAOT3TWovrNe4cJvqAuvPV26zErezm0eqo9rF%2B%3DFpFk_Pzh-q0Q%40mail.gmail.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM_kR7xyCZUMidEHdpHxOZV9hPfa2TXgZ7y5mzXM8jebFA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
