-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] SimpleBlocksIT testConcurrentAddBlock failing #122324
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
Comments
This has been muted on branch main Mute Reasons:
Build Scans: |
Pinging @elastic/es-core-infra (Team:Core/Infra) |
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
I think that blocks could be an area covered by distributed, but please send it back if I'm wrong. |
The fingerprints on that test point to us being owners. We'll take it. |
We apparently are able to add a block and then the cluster state indicates we don't have it. Seems potentially dangerous. |
I have gotten one more failure out of this: https://gradle-enterprise.elastic.co/s/kmqodxa5xlous. To me this seems related to the recent work on N-2 support and especially changes done in #119743. As I'm not up to date to that work, I'll relabel this for the indexing team. |
Pinging @elastic/es-distributed-indexing (Team:Distributed Indexing) |
Only one of concurrent `prepareAddBlock` calls actually wins a race to add the block, so we need to check `assertIndexHasBlock` if the add index block has been acknowledged Resolve elastic#122324
Build Scans:
Reproduction Line:
Applicable branches:
main
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
Issue Reasons:
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
The text was updated successfully, but these errors were encountered: