-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[TSVB] Set listener limit to abort signal correctly #132624
Conversation
...ins/vis_types/timeseries/server/lib/search_strategies/strategies/abstract_search_strategy.ts
Outdated
Show resolved
Hide resolved
…strategies/abstract_search_strategy.ts Co-authored-by: Tiago Costa <[email protected]>
… into tsvb-event-leak-warning
Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes LGTM, I tested it locally with a TSVB timeseries with 50 series, I cant see any warning on my kibana server
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
(cherry picked from commit eacbbbd)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit eacbbbd) Co-authored-by: Joe Reuter <[email protected]>
Fixes #132571
by creating a new abort signal per search instead of sharing across all searches of a request (the user controls how many searches are part of a single TSVB request).
Test by creating a TSVB timeseries vis with lots of series - there shouldn't be warnings in Kibana server logs.