Skip to content

[#1321] Fix scroll cursor leak inside searchScroll helper. #1322

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

Closed
wants to merge 1 commit into from

Conversation

abarre
Copy link

@abarre abarre commented Sep 24, 2020

I didn't find a way to test this change.
The leak is not visible in the client side but only in the server side during the scroll window.

@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Copy link
Member

@delvedor delvedor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix!
Regarding the test, you should add a new test case in this file to verify that the last call (if the conditions are met) is a clear scroll.

@abarre
Copy link
Author

abarre commented Oct 2, 2020

I will modify this PR in the next days. I had a quick look at the code and I see that the test code expect that the last request doesn't send a scroll_id in the response.
Can you confirm that this is a mistake and that in real life, all responses contain a scroll id ?

I didn't find the documentation on this point.

@delvedor
Copy link
Member

delvedor commented Oct 7, 2020

I've checked and the scroll_id is always present in the body, but it can change over time.
I've opened #1331 with the fix and the updated test.
Closing this, thank you a lot for contributing!

@delvedor delvedor closed this Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants