Investigate server background polling #32428
Comments
|
Pinging @elastic/kibana-operations |
jinmu03
added
the
Team:Core
|
Pinging @elastic/kibana-platform |
|
@pmoust i'm struggling to come up with a target heuristic for number of request, open connections, data transfer, etc. we depend on polling in some areas, it'll be a balance between functionality and dev time the lower we need to go. do you have any thoughts on how far we need to take this? |
Given that Kibana goes through a huge number of operation at init time, and we want to make sure those happen smoothly, would it make more sense to think about heuristics on a time scale? Example:
BTW these are NOT real-world suggestions and probably way off. I'd be really interested to see what a graph of startup looks like today, and think about how Kibana can throttle when its desirable to. WDYT? |
tylersmalley
changed the title
|
@timroes @tsullivan Who will be taking care of the Reporting? |
|
@jinmu03 rewriting the reporting polling to use Task Manager is on the Reporting roadmap for 7.x |
The license check is used to determine license status, e.g. whether it's expired or not. If we remove the poll-based license check, we'll need to lazily refresh license info whenever a license-restricted API endpoint is hit. We can optimize this by throttling the refresh, so we're not adding latency to every request. The @elastic/es-ui team has created a generic license-checker (#30299). Once X-Pack apps have migrated to using this system, we can incorporate this refresh logic into the system to block access to restricted APIs once the license expires or changes. However, this doesn't address blocking the user from accessing restricted UIs. We would probably need to update the client to poll the server and refresh the license info regularly (e.g. 1x a day). |
|
@tsullivan is there an issue tracking reporting/task manager integration? |
|
@jbudz it is in our roadmap spreadsheet, but there isn't an issue on it yet. It's something we are looking to do for 7.3 |
|
Remaining tasks have their own issues open, closing this out for now. |
Kibana has several discrete background polling operations. In one minute from startup in 8.0 we have 57 request in a red state, and 293 requests in a green state. In practice it's enough to put load on clusters and in between networking.
extremely rough estimates by application initiator:
This is an overview and meta issue to track high and low level improvements.
High level
combine requestsnot easily at a high levelcan we use the task manager?yesLow level
can this be checked once on startup?not easily, low impactonly start bulk uploader oncecan we remove the clusters abstraction?yes, but no impactcombine background checks for csv, png, and pdf into one requestThe text was updated successfully, but these errors were encountered: