Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[CI] BulkAfterWriteFsyncFailureIT testFsyncFailureDoesNotAdvanceLocalCheckpoints failing #110551

Closed
elasticsearchmachine opened this issue Jul 5, 2024 · 2 comments · Fixed by #110867
Closed

[CI] BulkAfterWriteFsyncFailureIT testFsyncFailureDoesNotAdvanceLocalCheckpoints failing #110551

elasticsearchmachine opened this issue Jul 5, 2024 · 2 comments · Fixed by #110867
Assignees
@kingherc
Labels
:Distributed Indexing/CRUD A catch all label for issues around indexing, updating and getting a doc by id. Not search. medium-risk An open issue or test failure that is a medium risk to future releases Team:Distributed Meta label for distributed team (obsolete) >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ':server:internalClusterTest' --tests "org.elasticsearch.action.bulk.BulkAfterWriteFsyncFailureIT.testFsyncFailureDoesNotAdvanceLocalCheckpoints" -Dtests.seed=D492149CFC74C8EC -Dtests.locale=sl-SI -Dtests.timezone=Etc/GMT+5 -Druntime.java=22

Applicable branches:
8.15

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: null

Issue Reasons:

  • [8.15] 3 failures in test testFsyncFailureDoesNotAdvanceLocalCheckpoints (2.7% fail rate)
  • [8.15] 3 failures in pipeline elasticsearch-periodic-platform-support (75.0% fail rate)
  • [8.15] 2.7% failure rate in test testFsyncFailureDoesNotAdvanceLocalCheckpoints (2.7% fail rate)

Note:
This issue was created using new, in-development muting automation. Please mind any issues.
@elasticsearchmachine elasticsearchmachine added :Distributed Indexing/CRUD A catch all label for issues around indexing, updating and getting a doc by id. Not search. >test-failure Triaged test failures from CI Team:Distributed Meta label for distributed team (obsolete) needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jul 5, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-distributed (Team:Distributed)

DaveCTurner added a commit that referenced this issue Jul 8, 2024
@DaveCTurner
AwaitsFix for #110551
9c0c708
DaveCTurner added a commit that referenced this issue Jul 8, 2024
@DaveCTurner
AwaitsFix for #110551
7b51ff6
@DaveCTurner
Copy link
Contributor

Muted in main (9c0c708) and 8.15 (7b51ff6).

@kingherc kingherc self-assigned this Jul 8, 2024
@kingherc kingherc added the low-risk An open issue or test failure that is a low risk to future releases label Jul 11, 2024
@elasticsearchmachine elasticsearchmachine removed the needs:risk Requires assignment of a risk label (low, medium, blocker) label Jul 11, 2024
@kingherc kingherc added medium-risk An open issue or test failure that is a medium risk to future releases and removed low-risk An open issue or test failure that is a low risk to future releases labels Jul 11, 2024
kingherc added a commit to kingherc/elasticsearch that referenced this issue Jul 15, 2024
@kingherc
Do not write dangling indices in a test
167e0f6 
So that the only expected disk write is from the bulk request.

Fixes elastic#110551
@kingherc kingherc mentioned this issue Jul 15, 2024
Merged
kingherc added a commit to kingherc/elasticsearch that referenced this issue Jul 15, 2024
@kingherc
Do not write dangling indices in a test (elastic#110867)
080a6c1 
So that the only expected disk write at the point of the assertion is from the bulk request. And not from the asynchronous runnable of updateDanglingIndicesInfo().

Fixes elastic#110551
elasticsearchmachine pushed a commit that referenced this issue Jul 15, 2024
@kingherc
Do not write dangling indices in a test (#110867) (#110869)
0fbde2c 
So that the only expected disk write at the point of the assertion is from the bulk request. And not from the asynchronous runnable of updateDanglingIndicesInfo().

Fixes #110551
@lkts lkts mentioned this issue Aug 13, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kingherc kingherc

Labels
:Distributed Indexing/CRUD A catch all label for issues around indexing, updating and getting a doc by id. Not search. medium-risk An open issue or test failure that is a medium risk to future releases Team:Distributed Meta label for distributed team (obsolete) >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Do not update dangling indices asynchronously in a test kingherc/elasticsearch
3 participants
@DaveCTurner @kingherc @elasticsearchmachine