Handling for 413 entity too large in BulkIndexer

[mauri870]

While investigating https://github.com/elastic/ingest-dev/issues/3677, I noticed that this package does not handle a 413 Entity Too Large status from Elasticsearch. Even with batching, in specific use cases like in Beats (which may include large stack traces in documents), a batch can still exceed http.max_content_length, the maximum request size in Elasticsearch, which defaults to 100MB.

[mauri870]

Closing this since it is handled in the elasticsearchexporter.

[kruskall]

This is still relevant, elasticsearchexporter has nothing to do with this repo