Skip to content
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

Feature request: _cat API for open scroll contexts #41376

Open
bra-fsn opened this issue Apr 19, 2019 · 4 comments
Open

Feature request: _cat API for open scroll contexts #41376

bra-fsn opened this issue Apr 19, 2019 · 4 comments

Comments

@bra-fsn
Copy link

@bra-fsn bra-fsn commented Apr 19, 2019

It would be nice to have a _cat endpoint, showing which scroll contexts are open with detailed information, like:

  • the scroll ID
  • opened since
  • the IP which opened it
  • the list of involved indices/segments
  • the associated query
  • the scroll timeout
  • anything else you may find useful

In investigating issues like #41337, this would be a big help.

@elasticmachine

This comment has been minimized.

Copy link
Collaborator

@elasticmachine elasticmachine commented Apr 19, 2019

@jakelandis

This comment has been minimized.

Copy link
Contributor

@jakelandis jakelandis commented Apr 25, 2019

In general this a good enhancement request. However we may not have access to all of the information in the OP. We will also want to add an API in addition to _cat to expose this type of information.

@bra-fsn

This comment has been minimized.

Copy link
Author

@bra-fsn bra-fsn commented May 2, 2019

The best would be if it could show the scroll's memory usage as well, making it super easy to see what causes JVM OOM or query rejects.

@bra-fsn

This comment has been minimized.

Copy link
Author

@bra-fsn bra-fsn commented Feb 14, 2020

I have a moderately sized cluster of 40 machines where several nodes die with OOM. According to the stats those have a very high number of open scroll contexts, but lacking this detailed info, I can't tell what app does this.
Could you please include anything which you currently have available? It would be a big help to investigate these kind of issues!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.