Skip to content

[CI] HdfsBlobStoreRepositoryTests class failing #127677

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
Closed
elasticsearchmachine opened this issue May 4, 2025 · 1 comment
Closed

[CI] HdfsBlobStoreRepositoryTests class failing #127677

elasticsearchmachine opened this issue May 4, 2025 · 1 comment
Labels
:Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Coordination Meta label for Distributed Coordination team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented May 4, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

undefined

Applicable branches:
8.19

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

undefined

Issue Reasons:

  • [8.19] 5 consecutive failures in class org.elasticsearch.repositories.hdfs.HdfsBlobStoreRepositoryTests
  • [8.19] 19 consecutive failures in step openjdk17_checkpart1_java-fips-matrix
  • [8.19] 18 consecutive failures in step openjdk21_checkpart1_java-matrix
  • [8.19] 17 consecutive failures in step openjdk17_checkpart1_java-matrix
  • [8.19] 18 consecutive failures in step openjdk22_checkpart1_java-matrix
  • [8.19] 18 consecutive failures in step graalvm-ce17_checkpart1_java-matrix
  • [8.19] 90 failures in class org.elasticsearch.repositories.hdfs.HdfsBlobStoreRepositoryTests (14.9% fail rate in 606 executions)
  • [8.19] 19 failures in step openjdk17_checkpart1_java-fips-matrix (100.0% fail rate in 19 executions)
  • [8.19] 18 failures in step openjdk21_checkpart1_java-matrix (100.0% fail rate in 18 executions)
  • [8.19] 17 failures in step openjdk17_checkpart1_java-matrix (100.0% fail rate in 17 executions)
  • [8.19] 18 failures in step openjdk22_checkpart1_java-matrix (100.0% fail rate in 18 executions)
  • [8.19] 18 failures in step graalvm-ce17_checkpart1_java-matrix (100.0% fail rate in 18 executions)
  • [8.19] 19 failures in pipeline elasticsearch-periodic (100.0% fail rate in 19 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >test-failure Triaged test failures from CI needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Distributed Coordination Meta label for Distributed Coordination team labels May 4, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@JeremyDahlgren JeremyDahlgren mentioned this issue May 4, 2025
Merged
JeremyDahlgren added a commit that referenced this issue May 4, 2025
@JeremyDahlgren
Adjust ForkJoinPool prefix in HdfsClientThreadLeakFilter (#127534) (#…
20a3b7f 
…127683)

Adds the ForkJoinPool.commonPool-worker- prefix to the
Thread getName().startsWith() checks in HdfsClientThreadLeakFilter.
This resolves the
"There are still zombie threads that couldn't be terminated"
errors in the Hdfs IT tests.

Closes #127676
Closes #127677
Closes #127678
Closes #127679

(cherry picked from commit 4408e38)
@JeremyDahlgren JeremyDahlgren added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels May 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Coordination Meta label for Distributed Coordination team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@elasticsearchmachine @JeremyDahlgren