Skip to content
This repository

Disable allocation: New indices allocation not to be disabled by default #2258

Closed
kimchy opened this Issue September 17, 2012 · 0 comments

1 participant

Shay Banon
Shay Banon
Owner

When setting cluster.routing.allocation.disable_allocation, it causes new indices primary shards to not be allocated. By default, new indices created should allow to, at the very least, allocate primary shards so they become operations. A new setting, cluster.routing.allocation.disable_new_allocation, allows to also disable "new" allocations.

Shay Banon kimchy closed this issue from a commit September 17, 2012
Shay Banon Disable allocation: New indices allocation not to be disabled by default
When setting cluster.routing.allocation.disable_allocation, it causes new indices primary shards to not be allocated. By default, new indices created should allow to, at the very least, allocate primary shards so they become operations. A new setting, cluster.routing.allocation.disable_new_allocation, allows to also disable "new" allocations.
closes #2258.
7924115
Shay Banon kimchy closed this in 7924115 September 17, 2012
Shay Banon kimchy referenced this issue from a commit September 17, 2012
Shay Banon Disable allocation: New indices allocation not to be disabled by default
When setting cluster.routing.allocation.disable_allocation, it causes new indices primary shards to not be allocated. By default, new indices created should allow to, at the very least, allocate primary shards so they become operations. A new setting, cluster.routing.allocation.disable_new_allocation, allows to also disable "new" allocations.
closes #2258.
d362d3c
Alberto Paro aparo referenced this issue from a commit May 31, 2013
Commit has since been removed from the repository and is no longer available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.