Single node yellow cluster ISM index

OpenSearch
1

Versions:

OpenSearch: 2.19
Server: Amazon OpenSearch Server

Describe the issue:

There is a .opendistro-job-scheduler-lock index that was automatically created configured to 5 shards and 1 replica, but, as I have a single node instance, it makes the cluster go to yellow.

I found that this is a solved issue from the Index Management plugin on a fork but could not spot it upstream: Yellow cluster status on single-node fresh install · Issue #87 · wazuh/wazuh-indexer

I also am not able to confirm my plugin version, as it is informed as x.x.x.x

58**99 kraken                                unspecified
58**99 kraken-index-management-extension     x.x.x.x
58**99 opensearch-index-management           x.x.x.x

Additionally, I found this thread stating it is a critical plugin and it should not be carelessly handled [FEATURE] Make the job scheduler lock index a system index · Issue #305 · opensearch-project/job-scheduler

So how do one fixes it so it stops being yellow without causing any other problems?

2

maybe try this
PUT /_index_template/system_indices_template
{
“index_patterns”: [“opendistro-job-scheduler-lock”],
“template”: {
“settings”: {
“auto_expand_replicas”: “0-all”
}
},
“priority”: 100
}’

3

what does this do?

4

@sousu This will allow auto expand replicas to all data nodes. It will also automatically scale down replicas number when node will be removed.
Instead of 0-all you can set 0-3 to expand to maximum 3 replicas.

.opendistro-job-scheduler-lock index is not configured with auto_expand_replicas when it is created.

1 Like