Just Pushed: Cluster / Index level allocation filtering


(Shay Banon) #1

First step at better control over how shards are allocated in a cluster was
just pushed, allowing to control which nodes (based on custom attributes) an
index can be allocated on. It comes with a nice side affect of being able
to decommission nodes even if the replica count is 0.

Here is the issue:
https://github.com/elasticsearch/elasticsearch/issues/1311.

-shay.banon


(ppearcy) #2

Cool stuff. Thanks for this feature!

On Sep 8, 5:31 am, Shay Banon kim...@gmail.com wrote:

First step at better control over how shards are allocated in a cluster was
just pushed, allowing to control which nodes (based on custom attributes) an
index can be allocated on. It comes with a nice side affect of being able
to decommission nodes even if the replica count is 0.

Here is the issue:https://github.com/elasticsearch/elasticsearch/issues/1311.

-shay.banon


(Berkay Mollamustafaoglu-2) #3

Great! This will enable several use cases for us.

Regards,
Berkay Mollamustafaoglu
mberkay on yahoo, google and skype

On Thu, Sep 8, 2011 at 7:31 AM, Shay Banon kimchy@gmail.com wrote:

First step at better control over how shards are allocated in a cluster was
just pushed, allowing to control which nodes (based on custom attributes) an
index can be allocated on. It comes with a nice side affect of being able
to decommission nodes even if the replica count is 0.

Here is the issue:
https://github.com/elasticsearch/elasticsearch/issues/1311.

-shay.banon


(system) #4