# Data too large, data for \[\<transport\_request\>\]

**URL:** <https://discuss.elastic.co/t/data-too-large-data-for-transport-request/241702>\
**Category:** Elasticsearch\
**Tags:** docker, es-hadoop\
**Created:** [July 17, 2020, 5:48pm UTC](https://discuss.elastic.co/t/data-too-large-data-for-transport-request/241702 "2020-07-17T17:48:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dawood](https://avatars.discourse-cdn.com/v4/letter/d/7feea3/32.png) [@Dawood](https://discuss.elastic.co/u/Dawood)\
**Post date:** [July 17, 2020, 5:48pm UTC](https://discuss.elastic.co/t/data-too-large-data-for-transport-request/241702/1 "2020-07-17T17:48:37Z")

</div>

i got the following in elasticsearch container logs:  
log:[parent] Data too large, data for [\<transport\_request\>] would be [1020455062/973.1mb], which is larger than the limit of [1011774259/964.9mb], real usage: [1020454800/973.1mb], new bytes reserved: [262/262b]

After a research i find that this is the solution:  
modify java options via environment ES\_JAVA\_OPTS to increase heap size

[6:20](https://nvidia.slack.com/archives/D01750XP6D8/p1594826433006200)

increase both values at the same time Xms and Xmx.

I made the change and change it to 2gb instead of 1gb in both. After the change the pods failed to start with the following log:  
{"type": "server", "timestamp": "2020-07-17T17:41:36,200Z", "level": "INFO", "component": "o.e.c.s.MasterService", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-0", "message": "node-join[{elasticsearch-master-1}{Qh\_vIzeDRlyGuFCiXMnjKg}{dLaiKIj7SIaTJryxi3bz2g}{10.42.1.98}{10.42.1.98:9300}{dilm}{ml.machine\_memory=4294967296, ml.max\_open\_jobs=20, xpack.installed=true} join existing leader], term: 55, version: 37066, delta: added {{elasticsearch-master-1}{Qh\_vIzeDRlyGuFCiXMnjKg}{dLaiKIj7SIaTJryxi3bz2g}{10.42.1.98}{10.42.1.98:9300}{dilm}{ml.machine\_memory=4294967296, ml.max\_open\_jobs=20, xpack.installed=true}}", "cluster.uuid": "pQepCBd7RBiiN9UQHlvppA", "node.id": "IX4HsayRQzqHk1I1K6K5Lg" }

7/17/2020 8:41:45 PM {"type": "server", "timestamp": "2020-07-17T17:41:45,216Z", "level": "INFO", "component": "o.e.c.s.ClusterApplierService", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-0", "message": "added {{elasticsearch-master-1}{Qh\_vIzeDRlyGuFCiXMnjKg}{dLaiKIj7SIaTJryxi3bz2g}{10.42.1.98}{10.42.1.98:9300}{dilm}{ml.machine\_memory=4294967296, ml.max\_open\_jobs=20, xpack.installed=true}}, term: 55, version: 37066, reason: Publication{term=55, version=37066}", "cluster.uuid": "pQepCBd7RBiiN9UQHlvppA", "node.id": "IX4HsayRQzqHk1I1K6K5Lg" }

Please assist.  
Thanks,  
Dawood

---

<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 14, 2020, 5:48pm UTC](https://discuss.elastic.co/t/data-too-large-data-for-transport-request/241702/2 "2020-08-14T17:48:39Z")

</div>

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