[Remote Storage][BUG] Don't fail remote store recovery for shards when there is actually no data in remote store. #16443
Labels
bug
Something isn't working
Storage:Durability
Issues and PRs related to the durability framework
Storage:Remote
Describe the bug
During index creation, there can be cases where some shards fail to initialize, often due to issues like exceeded disk usage on a node. Despite this partial failure, the index creation is considered successful, and we proceed to upload the remote index path file. This situation leads to a RED cluster status due to unassigned shards. When we attempt a remote store recovery in this state, it shows successful recovery for every shard even though the shards are still unassigned:
Response of Remote Restore API.
We see this stack trace in master logs.
Related component
Storage:Durability
To Reproduce
test-index1
test-index1
into new indexsplit-index-after-full-storage
with atleast 2 primary shards.split-index-after-full-storage
will get initialised on node2 and the shard on node1 will remains unassigned. This will lead to RED cluster state.Expected behavior
We should not see the stack trace for recovery failure. Instead we should see info that there is no data on remote to be recovered.
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.
The text was updated successfully, but these errors were encountered: