-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Segment Replication][BUG] Global checkpoint out of sync with local checkpoint on replica #2873
Comments
Looking into it. |
I followed repro steps but not able to replicate this issue. I tried multiple doc ingestions with ~10MB payload but didn't see this error. I tried increasing the payload to 20MBs in a single document but that also didn't help. Though identified a different issue, tracked in #4195 Steps followed
b. index settings
This issue was reported a while (4 months) ago after which multiple changes have happened. It might have been fixed with recent changes. @Poojita-Raj : I will try to repro this few more times with variations such more replicas, bigger payload size etc. If I am not able to repro, I will close this issue for now. |
Closing it for now as non-reproducible. |
Re-opening this found this issue while running below test in continuation. The
|
Sample failure trace shows that replica's local checkpoint (
|
Tried to reproduce this using below gradle command but it pops-up rarely. With #4224 hoping to see this go away completely (thanks @mch2 for the fix).
|
Closing this as probable fix #4224 is merged. |
Describe the bug
On replicas for segment replication, the global and local checkpoints are out of sync in 2 situations - (1) during recovery and (2) while waiting for indexed segment files to reach the replica from the primary. We want to avoid the failure in the latter scenario.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
To avoid the above failure due to the global and local checkpoints being out of sync for replica in segment replication
The text was updated successfully, but these errors were encountered: