# Encountered a retryable error. Will Retry with exponential backoff code=\>413

**URL:** <https://discuss.elastic.co/t/encountered-a-retryable-error-will-retry-with-exponential-backoff-code-413/234331>\
**Category:** Logstash\
**Created:** [May 26, 2020, 12:34pm UTC](https://discuss.elastic.co/t/encountered-a-retryable-error-will-retry-with-exponential-backoff-code-413/234331 "2020-05-26T12:34:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [May 26, 2020, 3:22pm UTC](https://discuss.elastic.co/t/encountered-a-retryable-error-will-retry-with-exponential-backoff-code-413/234331/2 "2020-05-26T15:22:27Z")

</div>

413 indicates the payload that logstash is sending to elasticsearch is too large. It does not really make sense for the elasticsearch output to retry this, because if the payload is too large the first time then it will still be too large when retried.

If you want to change it at the elasticsearch end you could increase http.max\_content\_length from its default of 100MB, but a better solution might be to reduce pipeline.batch.size in logstash.

---

_[View the full topic](https://discuss.elastic.co/t/encountered-a-retryable-error-will-retry-with-exponential-backoff-code-413/234331)._