# Why does ES not log Index rejection exceptions

**URL:** <https://discuss.elastic.co/t/why-does-es-not-log-index-rejection-exceptions/1766>\
**Category:** Elasticsearch\
**Created:** [June 2, 2015, 6:27pm UTC](https://discuss.elastic.co/t/why-does-es-not-log-index-rejection-exceptions/1766 "2015-06-02T18:27:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vangap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vangap/32/44927_2.png) [@vangap](https://discuss.elastic.co/u/vangap)\
**Post date:** [June 2, 2015, 6:27pm UTC](https://discuss.elastic.co/t/why-does-es-not-log-index-rejection-exceptions/1766/1 "2015-06-02T18:27:12Z")

</div>

I see that there was a indexing rejection error in ES client logs, that queue size limit of (200) is reached.  
But, I don't see this error in ES logs. logging level is INFO in logging.yml  
Do I have to make it to DEBUG to see this error?

Thanks.

---

<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 6, 2017, 12:10am UTC](https://discuss.elastic.co/t/why-does-es-not-log-index-rejection-exceptions/1766/2 "2017-07-06T00:10:08Z")

</div>

Closed on July 6, 2017, 12:10am UTC