# 413 Request Entity Too Large - metricbeat error on elected MASTER node

**URL:** <https://discuss.elastic.co/t/413-request-entity-too-large-metricbeat-error-on-elected-master-node/278732>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [July 15, 2021, 3:46am UTC](https://discuss.elastic.co/t/413-request-entity-too-large-metricbeat-error-on-elected-master-node/278732 "2021-07-15T03:46:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon17386273](https://avatars.discourse-cdn.com/v4/letter/a/d2c977/32.png) [@anon17386273](https://discuss.elastic.co/u/anon17386273)\
**Post date:** [July 15, 2021, 3:46am UTC](https://discuss.elastic.co/t/413-request-entity-too-large-metricbeat-error-on-elected-master-node/278732/1 "2021-07-15T03:46:27Z")

</div>

Is there a limitation that metricbeat can collect from the elected MASTER node?  
I have 300 data nodes with metricbeats having no issue running but when it comes to the collecting metrics from the elected MASTER, i encountered the following error

```auto
[elasticsearch]	elasticsearch/client.go:224	failed to perform any bulk index operations: 413 Request Entity Too Large:

```

I enabled debug logging, all i see is massive amount of json fields and values outputs, follow by the appearance of the "413 request entity too large" error.

I tried the configuration below but no avail  
bulk\_max\_size=1  
bulk\_max\_bytes: 10485760

Any help is appreciated on this. thank you

---

<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:** [August 12, 2021, 5:47am UTC](https://discuss.elastic.co/t/413-request-entity-too-large-metricbeat-error-on-elected-master-node/278732/2 "2021-08-12T05:47:08Z")

</div>

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