Shard Allocation with multiple includes/excludes

Elastic Stack Elasticsearch
1

I am trying to setup Shard Allocation using multiple includes, although the
behavior is not what I would expect. I have read through the docs and
searched through the group, but I can't seem to figure out what I am doing
wrong. The following is the setup and some examples of what happened vs
what I expected when trying to allocate shards. If anyone has any insight
into this it would be greatly appreciated.

Three nodes set up the following way:

NODE0 -
node.nodeNum:0
node.nodeAlpha:A

NODE1 -
node.nodeNum:1
node.nodeAlpha:B

NODE2 -
node.nodeNum:2
node.nodeAlpha:A

When created my index Initially the shards are split evenly between nodes,
since I have no allocation setup [Expected]...but then things get strange...

  1. I setup the index to include 'nodeNum:1', then all shards go to NODE1
    [Expected]
  2. I then add include 'nodeAlpha:A', and the shards split up between NODE0
    & NODE2
    [Expected] - I would expect the shards not to move as we now have include =
    'nodeNum:1' & 'nodeAlpha:A', which would include all nodes
  3. If I then change the first include to 'nodeNum:0', the shards don't move
    [Expected] - I would expect the shards all to go to NODE0 as we now have
    include = 'nodeNum:0' & 'nodeAlpha:A', which are both settings for NODE0
2

Robert - this may help -

Otis

Search Analytics - Cloud Monitoring Tools & Services | Sematext
Scalable Performance Monitoring - Sematext Monitoring | Infrastructure Monitoring Service

On Friday, July 13, 2012 3:11:45 PM UTC-4, Robert wrote:

I am trying to setup Shard Allocation using multiple includes, although
the behavior is not what I would expect. I have read through the docs and
searched through the group, but I can't seem to figure out what I am doing
wrong. The following is the setup and some examples of what happened vs
what I expected when trying to allocate shards. If anyone has any insight
into this it would be greatly appreciated.

Three nodes set up the following way:

NODE0 -
node.nodeNum:0
node.nodeAlpha:A

NODE1 -
node.nodeNum:1
node.nodeAlpha:B

NODE2 -
node.nodeNum:2
node.nodeAlpha:A

When created my index Initially the shards are split evenly between nodes,
since I have no allocation setup [Expected]...but then things get strange...

  1. I setup the index to include 'nodeNum:1', then all shards go to NODE1
    [Expected]
  2. I then add include 'nodeAlpha:A', and the shards split up between NODE0
    & NODE2
    [Expected] - I would expect the shards not to move as we now have include
    = 'nodeNum:1' & 'nodeAlpha:A', which would include all nodes
  3. If I then change the first include to 'nodeNum:0', the shards don't move
    [Expected] - I would expect the shards all to go to NODE0 as we now have
    include = 'nodeNum:0' & 'nodeAlpha:A', which are both settings for NODE0