What Does '0-all' Mean?

Elastic Stack Elasticsearch
1

Hi,

What does the setting '0-all' mean as a value to auto_expand_replicas? Is
there a '1-all'? 'N-all'?

BTW, '0-all' makes a lousy search term. Too much noise.

...Thanks,
...Ken

2

Following up a bit --- I am trying to increase the number of replicas in
the percolator and would like to maintain the auto-expand feature. If I
have the settings as:

"index" : {
    "number_of_replicas" : 2,
    "auto_expand_replicas" : "0-all"
}

and PUT the new settings as:

"index" : {
    "number_of_replicas" : 4,
    "auto_expand_replicas" : "0-all"
}

absolutely nothing happens except the original settings remain.

If I try:

"index" : {
    "number_of_replicas" : 2,
    "auto_expand_replicas" : "4-all"
}

it takes the setting and returns:

"index" : {
    "number_of_replicas" : 4,
    "auto_expand_replicas" : "4-all"
}

and sets up 6 unassigned shards which never get initialized and the cluster
stays in yellow. The percolator index is only a few thousand entries, so I
would expect the new replicas to get created quickly, but an hour later,
they are still unassigned.

So, how is this supposed to work? I'm confused.

...Thanks,
...Ken

On Thu, Feb 2, 2012 at 9:30 AM, Kenneth Loafman
kenneth.loafman@gmail.comwrote:

Hi,

What does the setting '0-all' mean as a value to auto_expand_replicas? Is
there a '1-all'? 'N-all'?

BTW, '0-all' makes a lousy search term. Too much noise.

...Thanks,
...Ken

3

What are you after specifically? The auto expand replicas mainly make sense when an index has 1 shard, and it will automatically expand the number of replicas to fit the number of data nodes.

On Thursday, February 2, 2012 at 7:42 PM, Kenneth Loafman wrote:

Following up a bit --- I am trying to increase the number of replicas in the percolator and would like to maintain the auto-expand feature. If I have the settings as:

"index" : { 
    "number_of_replicas" : 2,
    "auto_expand_replicas" : "0-all"
}

and PUT the new settings as:

"index" : { 
    "number_of_replicas" : 4,
    "auto_expand_replicas" : "0-all"

}

absolutely nothing happens except the original settings remain.

If I try:

"index" : {
    "number_of_replicas" : 2,
    "auto_expand_replicas" : "4-all"

}

it takes the setting and returns:

"index" : {
    "number_of_replicas" : 4,
    "auto_expand_replicas" : "4-all"

}

and sets up 6 unassigned shards which never get initialized and the cluster stays in yellow. The percolator index is only a few thousand entries, so I would expect the new replicas to get created quickly, but an hour later, they are still unassigned.

So, how is this supposed to work? I'm confused.

...Thanks,
...Ken

On Thu, Feb 2, 2012 at 9:30 AM, Kenneth Loafman <kenneth.loafman@gmail.com (mailto:kenneth.loafman@gmail.com)> wrote:

Hi,

What does the setting '0-all' mean as a value to auto_expand_replicas? Is there a '1-all'? 'N-all'?

BTW, '0-all' makes a lousy search term. Too much noise.

...Thanks,
...Ken

4

Specifically, more _percolator replicas to increase the number of
percolator engines. I discovered in a later message that you can have only
one shard/replica per node, so what I did was increase the number of nodes
on each machine in the percolator cluster (we're using a percolator cluster
and a search cluster since we put a very heavy load on the percolator and
that was affecting search).

I played with other numbers than 0, like 4-all, with no luck. The
additional replicas remained unassigned and the cluster state stays yellow.
I am still curious what the intent of the parameter is since I can find
no documentation.

On Sun, Feb 5, 2012 at 5:23 AM, Shay Banon kimchy@gmail.com wrote:

What are you after specifically? The auto expand replicas mainly make
sense when an index has 1 shard, and it will automatically expand the
number of replicas to fit the number of data nodes.

On Thursday, February 2, 2012 at 7:42 PM, Kenneth Loafman wrote:

Following up a bit --- I am trying to increase the number of replicas in
the percolator and would like to maintain the auto-expand feature. If I
have the settings as:

"index" : {
    "number_of_replicas" : 2,
    "auto_expand_replicas" : "0-all"
}

and PUT the new settings as:

"index" : {
    "number_of_replicas" : 4,
    "auto_expand_replicas" : "0-all"
}

absolutely nothing happens except the original settings remain.

If I try:

"index" : {
    "number_of_replicas" : 2,
    "auto_expand_replicas" : "4-all"
}

it takes the setting and returns:

"index" : {
    "number_of_replicas" : 4,
    "auto_expand_replicas" : "4-all"
}

and sets up 6 unassigned shards which never get initialized and the
cluster stays in yellow. The percolator index is only a few thousand
entries, so I would expect the new replicas to get created quickly, but an
hour later, they are still unassigned.

So, how is this supposed to work? I'm confused.

...Thanks,
...Ken

On Thu, Feb 2, 2012 at 9:30 AM, Kenneth Loafman <kenneth.loafman@gmail.com

wrote:

Hi,

What does the setting '0-all' mean as a value to auto_expand_replicas? Is
there a '1-all'? 'N-all'?

BTW, '0-all' makes a lousy search term. Too much noise.

...Thanks,
...Ken

5

Specifically, more _percolator replicas to increase the number of
percolator engines. I discovered in a later message that you can have only
one shard/replica per node, so what I did was increase the number of nodes
on each machine in the percolator cluster (we're using a percolator cluster
and a search cluster since we put a very heavy load on the percolator and
that was affecting search).

I played with other numbers than 0, like 4-all, with no luck. The
additional replicas remained unassigned and the cluster state stays yellow.
I am still curious what the intent of the parameter is since I can find
no documentation.

On Sun, Feb 5, 2012 at 5:23 AM, Shay Banon kimchy@gmail.com wrote:

What are you after specifically? The auto expand replicas mainly make
sense when an index has 1 shard, and it will automatically expand the
number of replicas to fit the number of data nodes.

On Thursday, February 2, 2012 at 7:42 PM, Kenneth Loafman wrote:

Following up a bit --- I am trying to increase the number of replicas in
the percolator and would like to maintain the auto-expand feature. If I
have the settings as:

"index" : {
    "number_of_replicas" : 2,
    "auto_expand_replicas" : "0-all"
}

and PUT the new settings as:

"index" : {
    "number_of_replicas" : 4,
    "auto_expand_replicas" : "0-all"
}

absolutely nothing happens except the original settings remain.

If I try:

"index" : {
    "number_of_replicas" : 2,
    "auto_expand_replicas" : "4-all"
}

it takes the setting and returns:

"index" : {
    "number_of_replicas" : 4,
    "auto_expand_replicas" : "4-all"
}

and sets up 6 unassigned shards which never get initialized and the
cluster stays in yellow. The percolator index is only a few thousand
entries, so I would expect the new replicas to get created quickly, but an
hour later, they are still unassigned.

So, how is this supposed to work? I'm confused.

...Thanks,
...Ken

On Thu, Feb 2, 2012 at 9:30 AM, Kenneth Loafman <kenneth.loafman@gmail.com

wrote:

Hi,

What does the setting '0-all' mean as a value to auto_expand_replicas? Is
there a '1-all'? 'N-all'?

BTW, '0-all' makes a lousy search term. Too much noise.

...Thanks,
...Ken