Open ashking94 opened 1 month ago
opensearch-master1 | [2024-09-20T09:00:43,097][INFO ][o.o.c.r.a.AllocationService] [opensearch-master1] Cluster health status changed from [RED] to [GREEN] (reason: [shards started [[index1][0]]]).
Curious why the shard was started after closed index. May be some race in shard allocation.
[Triage - attendees 1 2 3] Thanks @ashking94 for filing the issue.
Do we have the logs corresponding to the health status change from GREEN/YELLOW to RED to help us understand the duration of RED status ? Is it possible that the close & re-open operation was performed by two consecutive reroute
calls.
Hi @rajiv-kv, I have already shared the logs in the issue description. Let me know what else do you need.
Describe the bug
As of today, when an index is closed, it makes the cluster red temporarily until the shard has started. I am able to see this issue in both conventional document replication cluster as well as remote store enabled clusters.
Logs on a remote store enabled cluster
Logs on doc rep clusters
This problem may be aggravated in remote store enabled cluster due to existing behaviour where the translog is downloaded from remote store. This, however, is being fixed now.
Related component
Cluster Manager
To Reproduce
Expected behavior
I am not very sure if the cluster should really turn red here or not. This gives a false sense of underlying issue that may be causing red cluster. IMHO the cluster should remain green during the close index is happening.
Additional Details
NA