-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] Test Failure CcrRetentionLeaseIT.testRetentionLeaseIsRenewedDuringRecovery #39268
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
Labels
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
>test-failure
Triaged test failures from CI
Comments
Pinging @elastic/es-distributed |
This was referenced Feb 21, 2019
I think it's a race condition in the test and I know how to address it. I will try to get to in the next few days. I am so sorry to the team for the disruption caused by this test. |
Build-stats link |
jasontedor
added a commit
that referenced
this issue
Feb 22, 2019
This commit adds some additional logging to a failing CCR retention lease test so that the nature of the failure can be completely understood before attempting to push a fix. Relates #39268
jasontedor
added a commit
that referenced
this issue
Feb 23, 2019
Finally! This commit should fix the issues with the CCR retention lease that has been plaguing build failures. The issue here is that we are trying to prevent the clear session requests from being executed until after we have been able to validate that retention leases are being renewed. However, we were only blocking the clear session requests but not blocking them when they are proxied through another node. This commit addresses that. Relates #39268
jasontedor
added a commit
that referenced
this issue
Feb 23, 2019
Finally! This commit should fix the issues with the CCR retention lease that has been plaguing build failures. The issue here is that we are trying to prevent the clear session requests from being executed until after we have been able to validate that retention leases are being renewed. However, we were only blocking the clear session requests but not blocking them when they are proxied through another node. This commit addresses that. Relates #39268
jasontedor
added a commit
that referenced
this issue
Feb 23, 2019
Finally! This commit should fix the issues with the CCR retention lease that has been plaguing build failures. The issue here is that we are trying to prevent the clear session requests from being executed until after we have been able to validate that retention leases are being renewed. However, we were only blocking the clear session requests but not blocking them when they are proxied through another node. This commit addresses that. Relates #39268
This test has not failed since the fix that I pushed last night. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
>test-failure
Triaged test failures from CI
Build:
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+internalClusterTest/1654/console
Unable to reproduce locally:
Failure trace:
Possibly related to #39011
The text was updated successfully, but these errors were encountered: