Curator: During Shrink, replicas assigned to ignored nodes

Hi All,

ElasticSearch 6.5.4 and Curator 5.6

I'm testing out curator and have it successfully moving shards from 'hot' nodes to 'warm' nodes.

I'm now looking at shrinking the shards down to 3 (3 warm nodes). This is working 'sort of' except that the replica shards are being initialised on my 'hot' / nodes in the ignored list then being moved back to warm once they have been initialised on the wrong nodes.

Also I'm seeing all 3 active shards being created on one 'warm' node then again being redistributed once the process in complete.

Is there anything wrong with my config or a feature of curator?

My curator config is this:

action: shrink
description: >-
Shrink selected indices on the node with the most available space.
Delete source index after successful shrink, then reroute the shrunk
index with the provided parameters.
ignore_empty_list: True
shrink_node: DETERMINISTIC
permit_masters: False
exclude_nodes: ["", "", "", "", "", "", "", "", ""]
number_of_shards: 3
number_of_replicas: 1
shrink_suffix: '-shrink'
delete_after: True
allocation_type: include
key: boxtype
value: warm
wait_for_active_shards: 1
index.codec: best_compression
wait_for_completion: True
wait_for_rebalance: True
wait_interval: 9
max_wait: -1
- filtertype: pattern
kind: prefix
value: graylog_
- filtertype: age
source: creation_date
direction: older
unit: hours
unit_count: 80
- filtertype: age
source: creation_date
direction: younger
unit: hours
unit_count: 100

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.