On large cluster does it make sense to tweak these or diable them?
cluster.routing.allocation.allow_rebalance
cluster.routing.allocation.cluster_concurrent_rebalance
cluster.routing.allocation.node_initial_primaries_recoveries
cluster.routing.allocation.node_concurrent_recoveries
cluster.routing.allocation.disable_new_allocation
cluster.routing.allocation.disable_allocation
cluster.routing.allocation.disable_replica_allocation
cluster.routing.allocation.same_shard.host
indices.recovery.concurrent_streams
--
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/CAOT3TWo-ic_pp0sYML0TViEK81vDgkhQKTWhqPGPXPN_uxaBdQ%40mail.gmail.com .
For more options, visit https://groups.google.com/groups/opt_out .
warkolm
(Mark Walkom)
January 30, 2014, 9:55pm
2
Probably not disable, but tweak some of them, sure.
What are you trying to achieve?
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com
On 31 January 2014 08:49, Mohit Anchlia mohitanchlia@gmail.com wrote:
On large cluster does it make sense to tweak these or diable them?
cluster.routing.allocation.allow_rebalance
cluster.routing.allocation.cluster_concurrent_rebalance
cluster.routing.allocation.node_initial_primaries_recoveries
cluster.routing.allocation.node_concurrent_recoveries
cluster.routing.allocation.disable_new_allocation
cluster.routing.allocation.disable_allocation
cluster.routing.allocation.disable_replica_allocation
cluster.routing.allocation.same_shard.host
indices.recovery.concurrent_streams
--
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/CAOT3TWo-ic_pp0sYML0TViEK81vDgkhQKTWhqPGPXPN_uxaBdQ%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/CAEM624amKdX3H3E3yaNrHi3Dt2zz7BdP_qss7FDFp8A8vSey3g%40mail.gmail.com .
For more options, visit https://groups.google.com/groups/opt_out .
No impact to the cluster with regards to the high response times when new
node is added or dead node joins the cluster.
On Thu, Jan 30, 2014 at 1:55 PM, Mark Walkom markw@campaignmonitor.com wrote:
Probably not disable, but tweak some of them, sure.
What are you trying to achieve?
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com
On 31 January 2014 08:49, Mohit Anchlia mohitanchlia@gmail.com wrote:
On large cluster does it make sense to tweak these or diable them?
cluster.routing.allocation.allow_rebalance
cluster.routing.allocation.cluster_concurrent_rebalance
cluster.routing.allocation.node_initial_primaries_recoveries
cluster.routing.allocation.node_concurrent_recoveries
cluster.routing.allocation.disable_new_allocation
cluster.routing.allocation.disable_allocation
cluster.routing.allocation.disable_replica_allocation
cluster.routing.allocation.same_shard.host
indices.recovery.concurrent_streams
--
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/CAOT3TWo-ic_pp0sYML0TViEK81vDgkhQKTWhqPGPXPN_uxaBdQ%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/CAEM624amKdX3H3E3yaNrHi3Dt2zz7BdP_qss7FDFp8A8vSey3g%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/CAOT3TWrenfHdUhLOpwFzDDBjk10yxiCbMbfs_rWPszGRSbBJiA%40mail.gmail.com .
For more options, visit https://groups.google.com/groups/opt_out .