When the existing shards allocator would timeout in batch mode, we would need to attempt another reroute such that next iteration is in line. Currently, applyStartedShards, applyFailedShards, async fetch, etc would internally trigger a subsequent reroute from the previous batch. But this behaviour might not be guaranteed.
[Triage - attendees 12]
@imRishN Thanks for creating this issue, could you make a pull request to address this or update the description to remove to make it clearer what should be done for another community member?
peternied
commented
2 months ago
Describe the bug
When the existing shards allocator would timeout in batch mode, we would need to attempt another reroute such that next iteration is in line. Currently, applyStartedShards, applyFailedShards, async fetch, etc would internally trigger a subsequent reroute from the previous batch. But this behaviour might not be guaranteed.
Related PR comment - https://github.com/opensearch-project/OpenSearch/pull/14848#discussion_r1689072743
Related component
Other
To Reproduce
Expected behavior
Trigger subsequent reroute on timeout
Additional Details
Plugins Please list all plugins currently enabled.
Screenshots If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context Add any other context about the problem here.