-
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
[Reporting] Streaming CSV download appears to not be working #119540
Comments
Pinging @elastic/kibana-app-services (Team:AppServicesUx) |
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
Could this explain the issues experienced here https://discuss.elastic.co/t/csv-reporting-truncating-results-in-7-15-x/288142/4? After upgrading Kibana + ElasticSearch to 7.15.2 a semi-large CSV report would halt the entire Kibana instance (worked prior version 7.15.X). After scaling Kibana server vertically (more CPU and Memory resources) and increasing the following kibana.yml settings xpack.task_manager.max_workers: 100
xpack.reporting.queue.timeout: 600000 #Was configured prior 7.15.X upgrade
xpack.reporting.csv.maxSizeBytes: 104857600 #Was configured prior 7.15.X upgrade
xpack.reporting.csv.scroll.size: 10000 the kibana instance is now mostly able to finish the CSV report (Kibana still becomes unresponsive/slow), but it returns a truncated report containing a fraction of the expected amount of rows, and the size of it is only ~ 13 MB while the maxSizeBytes is set to 100 MB. This issue seems only to partly explain the kibana instance becoming unresponsive, but not the fact I get a truncated report? |
@TBragi This issue is about downloading the CSV from an embedded saved search panel in the Dashboard app. If that is how you've been generating the CSV, does generating a CSV from the Discover app work? I suspect what you are getting is a different issue. Do you see any errors in the Kibana server logs? Is Kibana crashing or restarting?
I recommend leaving this at the default setting of |
@tsullivan Thanks for the response,
This resulted in the following error message Looking at the Kibana logs it seems like it generates a part of the report (the low size, expected a factor 4 larger), but it fails to serve the file:
When I create a CSV report from the Discover App, the Kibana instance responds in the same way by slowing down and high cpu usage. The report is successfully generated, but it is truncated (it contains ~ 60.000 rows, but i expected ~300.000 rows) The Kibana logs tells the same
|
Potentially unrelated but we've also observed degradation in CSV reporting having jumpe form 6.8 to 7.15.1. A 400k row report that would previously complete successfully in a reasonable amount of time is now using an awful lot of CPU on the chosen Kibana instance to the point it becomes unresponsive for users and is eventually killed by our liveness probes Interestingly I spotted the scroll settings that I haven't previously seen on 6.x and have just started tweaking them to see the impact on things. In this instance I've bumped it up to 10000, but I imagine the scroll window has expired here, as the finished report is only ~100k rows, when the original discover query is ~400k
|
Kibana version: 7.15.1
Describe the bug:
Steps to reproduce:
Expected behavior:
As CSV Export scrolls through the data, it should stream partial content through the request so the connection doesn't time out.
Any additional context:
From @lucabelluccini
The text was updated successfully, but these errors were encountered: