I have a cluster with five nodes and I've specified that I'd like to
allocate a maximum of two shards to each node for indexes which are created
with five shards and two replicas of each (making ten shards to allocate in
total for each index). Occasionally I find that, at midnight when the new
index is created, a shard stays unassigned. For example, yesterday's index
was allocated as follows (brackets indicate primary shard):
node01 - (2) 3
node02 - 0 (4)
node03 - 2 (3)
node04 - (0) (1)
node05 - 1 4
This morning the new index was allocated as follows:
node01 - (2) 3
node02 - 2 (3)
node03 - (4)
node04 - 0 (1)
node05 - (0) 1
unassigned - 4
I now have to go in and manually move a shard from one of the nodes and the
shard is then allocated.
The settings for the indices are:
settings: {
index.analysis.analyzer.url_path_analyzer.type: custom
index.query.default_field: message
index.number_of_replicas: 1
index.number_of_shards: 5
index.auto_expand_replicas: false
index.routing.allocation.total_shards_per_node: 2
index.store.compress.tv: true
index.analysis.tokenizer.url_path_tokenizer.type: path_hierarchy
index.store.compress.stored: true
index.analysis.tokenizer.url_path_tokenizer.delimiter: /
index.cache.field.type: soft
index.analysis.analyzer.url_path_analyzer.tokenizer: url_path_tokenizer
index.version.created: 901199
index.uuid: XRooj-ZmRe2c58uYDzsMFQ
}
It's not using the standard Logstash settings (Logstash's elasticsearch
output is set to manage_templates => false).
Does anyone have any ideas as to what I've done wrong that is likely to be
causing these issues?
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/731c80d3-c6e0-4afe-b45d-92c70d774e2a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
