# NEST issue with ingesting PDFs

**URL:** <https://discuss.elastic.co/t/nest-issue-with-ingesting-pdfs/86871>\
**Category:** Elasticsearch\
**Created:** [May 23, 2017, 10:05pm UTC](https://discuss.elastic.co/t/nest-issue-with-ingesting-pdfs/86871 "2017-05-23T22:05:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![goodsammy1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/goodsammy1/32/17670_2.png) [@goodsammy1](https://discuss.elastic.co/u/goodsammy1)\
**Post date:** [May 23, 2017, 10:05pm UTC](https://discuss.elastic.co/t/nest-issue-with-ingesting-pdfs/86871/1 "2017-05-23T22:05:38Z")

</div>

Hi,

I am trying to index some PDF documents using NEST and ElasticSearch5.1. Most of them go thru fine. The larger ones (10 MB to 40 MB) throw either a "(413) Request Entity Too Large" or "System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host."

Can somebody please help me figure out what is the problem here?

UPDATE:  
I am led to believe that either the exceptions are not common or the work of uploading 10 - 40 MB of PDFs is uncommon. Can somebody please let me know if I am using Elastic in an unintended fashion?

---

<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:** [June 22, 2017, 3:43pm UTC](https://discuss.elastic.co/t/nest-issue-with-ingesting-pdfs/86871/3 "2017-06-22T15:43:21Z")

</div>

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