-
Notifications
You must be signed in to change notification settings - Fork 24.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
[CI] IndexShardIT » testMaybeFlush #52223
Comments
Pinging @elastic/es-distributed (:Distributed/Engine) |
Relates to #51905. |
Since #51905, we use the local checkpoint of the safe commit to calculate the number of uncommitted operations of a translog stats. If a periodic flush triggered by afterWriteOperation completes before we sync translog, then the last commit is not safe. We also need to sync translog from Engine instead of the translog so that we can advance the safe commit. Relates #51905 Closes #52223
This one failed again today: and the fix referenced in this issue seems to be in. Doesn't reproduce for me though. |
We aren't able to reproduce or figure out the reason that failed this test. This commit adds more assertions so we can narrow the scope. Relates #52223
Since elastic#51905, we use the local checkpoint of the safe commit to calculate the number of uncommitted operations of a translog stats. If a periodic flush triggered by afterWriteOperation completes before we sync translog, then the last commit is not safe. We also need to sync translog from Engine instead of the translog so that we can advance the safe commit. Relates elastic#51905 Closes elastic#52223
We aren't able to reproduce or figure out the reason that failed this test. This commit adds more assertions so we can narrow the scope. Relates elastic#52223
Since #51905, we use the local checkpoint of the safe commit to calculate the number of uncommitted operations of a translog stats. If a periodic flush triggered by afterWriteOperation completes before we sync translog, then the last commit is not safe. We also need to sync translog from Engine instead of the translog so that we can advance the safe commit. Relates #51905 Closes #52223
We aren't able to reproduce or figure out the reason that failed this test. This commit adds more assertions so we can narrow the scope. Relates #52223
@dnhatn has added more assertions here, but there haven't been any recent failures. I'll close this for now, but please report and reopen issue on any future failures. |
This test failed today on
Build scan: https://gradle-enterprise.elastic.co/s/i7xtizngehx4u It does not reproduce locally:
|
We still do not have enough info for this test failure. I've enabled the debug logs of the engine in this test. I am closing this issue again. Please reopen when it fails. |
This failed again in 7.x. Build scan, Jenkins |
And again, in 7.x: Build scan, Jenkins |
And again, in 7.x: Build scan, Jenkins |
Ang again, in 7.x: Build scan, Jenkins |
I am looking at this issue now. |
I've opened #54839. |
IndexShardIT#testMaybeFlush relies on the assumption that the safe commit and translog deletion policy have advanced after IndexShard#sync returns . This assumption does not hold if there's a race with the global checkpoint sync. Closes #52223
IndexShardIT#testMaybeFlush relies on the assumption that the safe commit and translog deletion policy have advanced after IndexShard#sync returns . This assumption does not hold if there's a race with the global checkpoint sync. Closes #52223
IndexShardIT#testMaybeFlush relies on the assumption that the safe commit and translog deletion policy have advanced after IndexShard#sync returns . This assumption does not hold if there's a race with the global checkpoint sync. Closes #52223
failed on master:
https://gradle-enterprise.elastic.co/s/izpnat3y374v4
The text was updated successfully, but these errors were encountered: