Search context is not cleaned when scroll search is cancelled #21126
Assignees
Labels
>bug
:Distributed/Task Management
Issues for anything around the Tasks API - both persistent and node level.
:Search/Search
Search-related issues that do not fall into other categories
Comments
imotov
added
>bug
:Search/Search
|
😢 |
|
I think I found the reason for the failure in these tests, but we need changes from #20767 to properly fix it. |
|
I'll get to it! I've got something so close to ready for review that I'd like to finish off first then I'll address your comments in #20767. |
imotov
added a commit
to imotov/elasticsearch
that referenced
this issue
Nov 11, 2016
…cancellation request before returning Currently the task cancellation command returns as soon as the top-level parent child is marked as cancelled. This create race conditions in tests where child tasks on other nodes may continue to run for some time after the main task is cancelled. This commit fixes this situation making task cancellation command to wait until it got propagated to all nodes that have child tasks. Closes elastic#21126
imotov
added a commit
that referenced
this issue
Nov 11, 2016
…cancellation request before returning Currently the task cancellation command returns as soon as the top-level parent child is marked as cancelled. This create race conditions in tests where child tasks on other nodes may continue to run for some time after the main task is cancelled. This commit fixes this situation making task cancellation command to wait until it got propagated to all nodes that have child tasks. Closes #21126
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cancelling search with scroll can leave some search contexts behind. See test failure in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-unix-compatibility/os=ubuntu/160/console
The text was updated successfully, but these errors were encountered: