-
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] Failures in IndexShardTests#testRollbackReplicaEngineOnPromotion #35850
Comments
Pinging @elastic/es-distributed |
Also we ran into this in a PR test over at #34112, there the error looks slightly different though: Build: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+pull-request-1/220/console
Note this is a different method ("testRestoreLocalHistoryFromTranslogOnPromotion") and on master, but same test class and at least correlated by time. Maybe related, just filing here in case this gives further hints. |
Another one that looks related, this time on master and again in "testRestoreLocalHistoryFromTranslogOnPromotion":
|
I muted both IndexShardTests#testRestoreLocalHistoryFromTranslogOnPromotion and IndexShardTests#testRollbackReplicaEngineOnPromotion on master and 6.x |
Thanks @cbuescher ! |
The were some errors that seems related with this one. They reproduce locally for master and 6.x:
Output:
It actually leads to a timeout. I am not muting the test because fix seems to be applied soon. |
Test IndexShardTests.testOperationPermitOnReplicaShards has been muted in master and 6.x |
…term update (#36116) This commit changes how an operation which requires all index shard operations permits is executed when a primary term update is required: the operation and the update are combined so that the operation is executed after the primary term update under the same blocking operation. Closes #35850 Co-authored-by: Yannick Welsch <[email protected]>
…term update (#36116) This commit changes how an operation which requires all index shard operations permits is executed when a primary term update is required: the operation and the update are combined so that the operation is executed after the primary term update under the same blocking operation. Closes #35850 Co-authored-by: Yannick Welsch <[email protected]>
Build failure: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+intake/263/console
Reproduce line (doesn't reproduce locally for me so far):
The text was updated successfully, but these errors were encountered: