-
Notifications
You must be signed in to change notification settings - Fork 25k
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] org.elasticsearch.index.reindex.CancelTests #26758
Labels
:Distributed Indexing/CRUD
A catch all label for issues around indexing, updating and getting a doc by id. Not search.
>test
Issues or PRs that are addressing/adding tests
>test-failure
Triaged test failures from CI
Comments
andyb-elastic
added
:Reindex API
>test
Issues or PRs that are addressing/adding tests
labels
Sep 22, 2017
I'm going to snag this and see if I can reproduce it. |
nik9000
added a commit
that referenced
this issue
Jan 23, 2018
The test failure tracked by #26758 occurs when we cancel a running reindex request that has been sliced into many children. The main reindex response *looks* canceled but none of the children look canceled. This is super strange because for the main request to look canceled for any length of time one of the children has to be canceled. This change adds additional logging to the test so we have more to go on to debug this the next time it fails.
nik9000
added a commit
that referenced
this issue
Jan 23, 2018
The test failure tracked by #26758 occurs when we cancel a running reindex request that has been sliced into many children. The main reindex response *looks* canceled but none of the children look canceled. This is super strange because for the main request to look canceled for any length of time one of the children has to be canceled. This change adds additional logging to the test so we have more to go on to debug this the next time it fails.
Of course I can't reproduce it. But I've pushed some code that'll give us more information the next time it fails.... |
I pushed 6f64e97 to see if that'll track down the cause. Then it failed locally for me while I was testing the backport, tripping the new assertion! Maybe I found it! |
nik9000
added a commit
that referenced
this issue
Jan 30, 2018
This gives the test longer to block its updates. Now that we're checking if the updates actually blocked saw that they may not do so in the normal 10 seconds on a highly loaded system. And our jenkins machines often function like highly loaded systems. Maybe this fixes #26758!
I'm going to let this one stay closed. It it occurs again I'll reopen. |
lcawl
added
:Distributed Indexing/CRUD
A catch all label for issues around indexing, updating and getting a doc by id. Not search.
and removed
:Reindex API
labels
Feb 13, 2018
cbuescher
pushed a commit
that referenced
this issue
Feb 15, 2018
This gives the test longer to block its updates. Now that we're checking if the updates actually blocked saw that they may not do so in the normal 10 seconds on a highly loaded system. And our jenkins machines often function like highly loaded systems. Maybe this fixes #26758!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Indexing/CRUD
A catch all label for issues around indexing, updating and getting a doc by id. Not search.
>test
Issues or PRs that are addressing/adding tests
>test-failure
Triaged test failures from CI
It looks like the reindex response times out because some slice tasks don't complete in time (though they do appear to all acknowledge the cancellation). I couldn't find a cause. Neither of these reproduce, and they fail very rarely.
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+5.5+multijob-unix-compatibility/os=fedora/141
build-141-CancelTests.txt
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+5.5+multijob-unix-compatibility/os=fedora/147
build-147-CancelTests.txt
The text was updated successfully, but these errors were encountered: