# Csv reporting always failed win 5m records

**URL:** <https://discuss.elastic.co/t/csv-reporting-always-failed-win-5m-records/239072>\
**Category:** Kibana\
**Created:** [June 29, 2020, 8:24am UTC](https://discuss.elastic.co/t/csv-reporting-always-failed-win-5m-records/239072 "2020-06-29T08:24:17Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hari\_Krishnan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hari_krishnan/32/66696_2.png) [@Hari\_Krishnan](https://discuss.elastic.co/u/Hari_Krishnan)\
**Post date:** [June 29, 2020, 8:24am UTC](https://discuss.elastic.co/t/csv-reporting-always-failed-win-5m-records/239072/1 "2020-06-29T08:24:17Z")

</div>

Hi,

I was trying to share CSV with 5 million records which is only datatime and md5 . so size might be less even its 5 million records .  
I have 900 MB in limit in both  
xpack.reporting.csv.maxSizeBytes  
http.max\_content\_length

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [June 29, 2020, 10:55am UTC](https://discuss.elastic.co/t/csv-reporting-always-failed-win-5m-records/239072/2 "2020-06-29T10:55:49Z")

</div>

Hi @Hari_Krishnan,

How does it fail exactly? What do you see in the Kibana logs (you'd need to enable debug logs with `logging.verbose: true`)? How does your `kibana.yml` look like and what version of the stack you use?

Best,  
Oleg

---

<div class="post-metadata">

**Author:** ![Hari\_Krishnan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hari_krishnan/32/66696_2.png) [@Hari\_Krishnan](https://discuss.elastic.co/u/Hari_Krishnan)\
**Post date:** [June 29, 2020, 11:17am UTC](https://discuss.elastic.co/t/csv-reporting-always-failed-win-5m-records/239072/3 "2020-06-29T11:17:33Z")

</div>

logging.verbose: true in kibana.yml file  
Kibana version: 7.0.1  
ES version: 7.0.1

**Kibana.yml**  
xpack.reporting.csv.maxSizeBytes: 905890000  
xpack.reporting.queue.timeout: 120000  
logging.verbose: true

**elasticsearch.yml**  
http.max\_content\_length: 1000mb

/var/log/message output 🙂  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}  
tags":["reporting","csv","debug"],"pid":3703,"message":"executing scroll request"}

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [June 29, 2020, 11:21am UTC](https://discuss.elastic.co/t/csv-reporting-always-failed-win-5m-records/239072/4 "2020-06-29T11:21:40Z")

</div>

> [@Hari\_Krishnan](#):
>
> executing scroll request

Well, that's not an error and it's expected. [The Scroll API](https://www.elastic.co/guide/en/elasticsearch/client/java-rest/master/java-rest-high-search-scroll.html) is used to work with large data set. So it should eventually do the job, unless you have other errors in the logs?

---

<div class="post-metadata">

**Author:** ![Hari\_Krishnan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hari_krishnan/32/66696_2.png) [@Hari\_Krishnan](https://discuss.elastic.co/u/Hari_Krishnan)\
**Post date:** [June 29, 2020, 11:37am UTC](https://discuss.elastic.co/t/csv-reporting-always-failed-win-5m-records/239072/5 "2020-06-29T11:37:31Z")

</div>

This is last log output if i search using csv keyword

{"type":"log","@timestamp":"2020-06-29T11:27:50Z","tags":["reporting","csv","debug"],"pid":3703,"message":"executing clearScroll request"}  
{"type":"log","@timestamp":"2020-06-29T11:27:50Z","tags":["reporting","csv","debug"],"pid":3703,"message":"finished generating, total size in bytes: 13103907"}

Here i assume the total report size 13103907 (~13mb) and i have configuration more than that

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [June 29, 2020, 11:39am UTC](https://discuss.elastic.co/t/csv-reporting-always-failed-win-5m-records/239072/6 "2020-06-29T11:39:40Z")

</div>

> ["reporting","csv","debug"],"pid":3703,"message":"finished generating, total size in bytes: 13103907"}  
> Here i assume the total report size 13103907 (~13mb) and i have configuration more than that

But this log entry says that it's successfully completed, what doesn't work for you then? Also do you see any log entries with `"error"` tag at all?

---

<div class="post-metadata">

**Author:** ![Hari\_Krishnan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hari_krishnan/32/66696_2.png) [@Hari\_Krishnan](https://discuss.elastic.co/u/Hari_Krishnan)\
**Post date:** [June 29, 2020, 11:41am UTC](https://discuss.elastic.co/t/csv-reporting-always-failed-win-5m-records/239072/7 "2020-06-29T11:41:58Z")

</div>

in the UI it shows failed after 3 attempts, is there any location i can check for csv file ?

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [June 29, 2020, 2:58pm UTC](https://discuss.elastic.co/t/csv-reporting-always-failed-win-5m-records/239072/8 "2020-06-29T14:58:20Z")

</div>

I see, then there definitely should be some failure in the logs (with `logging.verbose: true`). Either try to find it in the **full** logs or share that here (please, remove any sensitive info you may have there).

---

<div class="post-metadata">

**Author:** ![Hari\_Krishnan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hari_krishnan/32/66696_2.png) [@Hari\_Krishnan](https://discuss.elastic.co/u/Hari_Krishnan)\
**Post date:** [July 1, 2020, 9:26am UTC](https://discuss.elastic.co/t/csv-reporting-always-failed-win-5m-records/239072/9 "2020-07-01T09:26:48Z")

</div>

**Attaching log**

[https://pastebin.com/XtQF89bv](https://pastebin.com/XtQF89bv)

---

<div class="post-metadata">

**Author:** ![Hari\_Krishnan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hari_krishnan/32/66696_2.png) [@Hari\_Krishnan](https://discuss.elastic.co/u/Hari_Krishnan)\
**Post date:** [July 2, 2020, 9:50am UTC](https://discuss.elastic.co/t/csv-reporting-always-failed-win-5m-records/239072/10 "2020-07-02T09:50:22Z")

</div>

Any Luck @azasypkin ?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 30, 2020, 9:50am UTC](https://discuss.elastic.co/t/csv-reporting-always-failed-win-5m-records/239072/11 "2020-07-30T09:50:23Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
