-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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
num_freed field in clear all scrolls response is incorrect #63171
Comments
If it's fairly easy I would like to try and fix this bug |
Pinging @elastic/es-search (:Search/Search) |
@stav29 Do you have an example to reproduce this ? |
@matriv in order to reproduce this you will - need to run DELETE /_search/scroll/_all (instead of passing a specific scroll id or some scroll id's in an array). It wouldn't matter how many active scrolls you have (even without active scrolls) you will get the number of nodes in your cluster in the num_freed field in the response. |
@stav29 Thx for the clarification, the current behaviour is the intended one, but it's not documented (regarding the |
This has been open for quite a while, and hasn't had a lot of interest. For now I'm going to close this as something we aren't planning on implementing. We can re-open it later if needed. |
Elasticsearch version (
bin/elasticsearch --7.8.1
):Plugins installed: []
JVM version (
java -11.0.6
):OS version (windows):
Description of the problem:
When I try to delete all scrolls using DELETE server:port/_search/scroll/_all
I get the number of nodes in the cluster in the num_freed field instead of the number of scrolls actually being deleted
The text was updated successfully, but these errors were encountered: