Hot-warm architecture , my index staying on hot and warm node same time

Plugins Index Management
, , ,
1

Hey All ,

I have hot-warm policy which is so basic ;
{
“policy_id”: “test”,
“schema_version”: 12,
“error_notification”: null,
“default_state”: “hot”,
“states”: [
{
“name”: “hot”,
“actions”: ,
“transitions”: [
{
“state_name”: “warm”,
“conditions”: {
“min_size”: “100mb”
}
}
]
},
{
“name”: “warm”,
“actions”: [
{
“allocation”: {
“require”: {
“temp”: “warm”
},
“wait_for”: false
}
}
],
“transitions”:
}
],
“ism_template”: [
{
“index_patterns”: [
“application-test*”
],
“priority”: 1
}
]
}

when I create first index its correctly assigning to hot ;
application-test-2022.10.01 0 p STARTED 295314 210.9mb 10.244.0.80 opensearch-cluster-data-hot-0
application-test-2022.10.01 0 r UNASSIGNED

after moving to the warm node I can see my index assigned both nodes;
application-test-2022.10.01 0 p STARTED 295314 210.9mb 10.244.0.80 opensearch-cluster-data-hot-0
application-test-2022.10.01 0 r STARTED 295314 210.9mb 10.244.0.81 opensearch-cluster-data-warm-0

can you please help me?I am struggling with this long time :frowning:

2

Okay , problem solved , replica count was 2 in my index settings but my node has one replica so when I tried move from hot to warm my index was staying on both node so I decrease the replica count before moving to warm I saw my index moved to the warm successfully