-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
EncryptedAzureBlobStoreRepositoryIntegTests.testLargeBlobCountDeletion failed to delete directory #67119
Labels
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
Team:Distributed
Meta label for distributed team (obsolete)
>test-failure
Triaged test failures from CI
Comments
DaveCTurner
added
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>test-failure
Triaged test failures from CI
labels
Jan 6, 2021
elasticmachine
added
the
Team:Distributed
Meta label for distributed team (obsolete)
label
Jan 6, 2021
Pinging @elastic/es-distributed (Team:Distributed) |
This is failing a few times a day so I've muted in 22a6811. |
fcofdez
added a commit
to fcofdez/elasticsearch
that referenced
this issue
Jan 8, 2021
Instead of executing all the delete request in parallel this commits introduces a change that allows the execution of delete requests in batches of 100 parallel deletions. The reason for this change is to avoid timeout failures when large number of files should be deleted as if we execute all of them in parallel a few slow requests could make the rest to fail due to timeouts, as there is an effective limit at the connection pool level. Additionally, this commit improves the error messages provided as previously we weren't including the blob name on deletion failures. Closes elastic#67119
fcofdez
added a commit
that referenced
this issue
Jan 13, 2021
Additionally, this commit improves the error messages provided as previously we weren't including the blob name on deletion failures. Closes #67119
fcofdez
added a commit
to fcofdez/elasticsearch
that referenced
this issue
Jan 13, 2021
Additionally, this commit improves the error messages provided as previously we weren't including the blob name on deletion failures. Closes elastic#67119 Backport of elastic#67210
fcofdez
added a commit
to fcofdez/elasticsearch
that referenced
this issue
Jan 13, 2021
Additionally, this commit improves the error messages provided as previously we weren't including the blob name on deletion failures. Closes elastic#67119 Backport of elastic#67210
This was referenced Jan 13, 2021
fcofdez
added a commit
that referenced
this issue
Jan 13, 2021
fcofdez
added a commit
that referenced
this issue
Jan 13, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
Team:Distributed
Meta label for distributed team (obsolete)
>test-failure
Triaged test failures from CI
Build scan: https://gradle-enterprise.elastic.co/s/odetfr6slb2ou/console-log?task=:x-pack:plugin:repository-encrypted:internalClusterTest
Repro line:
REPRODUCE WITH: ./gradlew ':x-pack:plugin:repository-encrypted:internalClusterTest' --tests "org.elasticsearch.repositories.encrypted.EncryptedAzureBlobStoreRepositoryIntegTests.testLargeBlobCountDeletion" -Dtests.seed=98E7E9A0B1D0E0E9 -Dtests.security.manager=true -Dtests.locale=vi-VN -Dtests.timezone=America/Swift_Current -Druntime.java=11
Reproduces locally?: No
Applicable branches: Only seen on a PR build against
master
Failure history: https://build-stats.elastic.co/goto/276c4165d436c9b560144e07e799de1d indicates that this was failing frequently until 2020-12-30 but then quietened down for a week.
Failure excerpt: Doesn't look very helpful:
Labelling this
snapshot/restore
suspecting something wrong inAzureBlobStore.deleteBlobDirectory
but this could be related to the encrypted repo tests instead.The text was updated successfully, but these errors were encountered: