-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Follower index goes to "failed" state when the retention lease period expires. #1466
Comments
Hi @ankitkala, @monusingh-1 , Can you confirm this behaviour? Early feedback is much appreciated. |
All indices are expected to moved to autopause. For the indices which moved to failed, can you check the application logs? |
Hi @ankitkala , For the failed indices, we could see the below logs:
Im not sure when did this index get the first pause. Before this i could see there is a pause for shardReplicationTask which has got triggered.
Is the index being marked because of these subsequent pause form different tasks? Also, can you confirm the below behaviour: Any index which doesnt undergo any change within the retention lease period (i.e retention lease expires without any change in documents in leader and hence no change in follower) goes to auto-pause ? |
Hi @ankitkala, can you help me understand on retention lease expiry ? is there any document which i can refer ? |
What is the bug?
When the retention lease period expires for few indices. Few of the indices are going to "AutoPaused" and few of the indices are going to "Failed" state without any exception/reason.
As per expectation, the indices should have gone to "AutoPaused" from the documentation. Is this expected scenario?
The text was updated successfully, but these errors were encountered: