# Marvel 2 HTTP content length exceeded 104857600 bytes

**URL:** https://discuss.elastic.co/t/marvel-2-http-content-length-exceeded-104857600-bytes/35138
**Category:** Elasticsearch
**Tags:** elastic-stack-monitoring
**Created:** [November 20, 2015, 9:54am UTC](https://discuss.elastic.co/t/marvel-2-http-content-length-exceeded-104857600-bytes/35138 "2015-11-20T09:54:35Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![kaem2111](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaem2111/32/24961_2.png) [@kaem2111](https://discuss.elastic.co/u/kaem2111)
#### Post date: [November 20, 2015, 9:54am UTC](https://discuss.elastic.co/t/marvel-2-http-content-length-exceeded-104857600-bytes/35138/1 "2015-11-20T09:54:35Z")

</div>

Hello team

I am using ES 2.0.0 + Marvel 2.0.0.  
Probably after some heavy indexing I am getting the periodical error in ES-log:

_[2015-11-20 10:35:45,199][WARN][shield.transport.netty] [by0kmh] Caught exception while handling client http traffic, closing connection [id: 0xe75b04f8, /10.205.114.251:17825 =\> /10.205.114.251:9200]_  
_org.jboss.netty.handler.codec.frame.TooLongFrameException: **HTTP content length exceeded 104857600 bytes**._  
_...._  
_[2015-11-20 10:35:45,200][ERROR][**marvel.agent.exporter.http**] failed sending data to [[http://10.205.114.251:9200/\_bulk](http://10.205.114.251:9200/_bulk)]: IOException[Error writing to server]_

and cannot recover from that even after reconfiguration and reinstalling marvel-agent

My questions:

1. is there a parameter for marvel.agent.exporter like flush\_size to limit the es\_bulk content?
2. which internal cache/counter/dataset I have to clear to throw away the existing buffer and continue to work?

Thanks in advanced!

---

<div class="post-metadata">

### Author: ![tanguy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy/32/6030_2.png) [@tanguy](https://discuss.elastic.co/u/tanguy)
#### Post date: [November 20, 2015, 1:05pm UTC](https://discuss.elastic.co/t/marvel-2-http-content-length-exceeded-104857600-bytes/35138/2 "2015-11-20T13:05:44Z")

</div>

Thanks for reporting Kaem.

There's a bug in marvel where you can fall in under certain circumstances... and I think you hit this one. It will be fixed in the next releases.

How many indices & shards do you have?

---

<div class="post-metadata">

### Author: ![kaem2111](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaem2111/32/24961_2.png) [@kaem2111](https://discuss.elastic.co/u/kaem2111)
#### Post date: [November 20, 2015, 10:04pm UTC](https://discuss.elastic.co/t/marvel-2-http-content-length-exceeded-104857600-bytes/35138/3 "2015-11-20T22:04:41Z")

</div>

Hello,  
I have 2 nodes, 100 indices and 423 shards

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [November 21, 2015, 6:00am UTC](https://discuss.elastic.co/t/marvel-2-http-content-length-exceeded-104857600-bytes/35138/4 "2015-11-21T06:00:25Z")

</div>

Side note, you should reduce your shard count. You are probably wasting resources 🙂

---

<div class="post-metadata">

### Author: ![kaem2111](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaem2111/32/24961_2.png) [@kaem2111](https://discuss.elastic.co/u/kaem2111)
#### Post date: [November 30, 2015, 11:02am UTC](https://discuss.elastic.co/t/marvel-2-http-content-length-exceeded-104857600-bytes/35138/5 "2015-11-30T11:02:48Z")

</div>

Hi

after upgrading to marvel 2.1 the issues was fixed.

thx

---

<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, 1:46pm UTC](https://discuss.elastic.co/t/marvel-2-http-content-length-exceeded-104857600-bytes/35138/6 "2017-07-06T13:46:41Z")

</div>


