# One node now failing after successful upgrade 6.8-\>7.4 day before

**URL:** <https://discuss.elastic.co/t/one-node-now-failing-after-successful-upgrade-6-8-7-4-day-before/204307>\
**Category:** Elasticsearch\
**Created:** [October 19, 2019, 11:58am UTC](https://discuss.elastic.co/t/one-node-now-failing-after-successful-upgrade-6-8-7-4-day-before/204307 "2019-10-19T11:58:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\
**Post date:** [October 19, 2019, 11:58am UTC](https://discuss.elastic.co/t/one-node-now-failing-after-successful-upgrade-6-8-7-4-day-before/204307/1 "2019-10-19T11:58:03Z")

</div>

Did an upgrade yesterday from 6.8 to 7.1.1 to 7.4  
Today I find one node out of 27 data nodes failing like below and wonder who and why are sending so large message(s):

```
[2019-10-19T13:53:43,380][DEBUG][o.e.a.a.c.n.i.TransportNodesInfoAction] [d1r2n1] failed to execute on node [FDZezqUCRYqLNHfGV6eECw]
org.elasticsearch.transport.RemoteTransportException: [es-mst3][<redacted>:9300][cluster:monitor/nodes/info[n]]
Caused by: org.elasticsearch.common.breaker.CircuitBreakingException: [parent] Data too large, data for [<transport_request>] would be [4061260842/3.7gb], which is larger than the limit of [4047097036/3.7gb], real usage: [4061245568/3.7gb], new bytes reserved: [15274/14.9kb], usages [request=0/0b, fielddata=0/0b, in_flight_requests=15274/14.9kb, accounting=0/0b]
        at org.elasticsearch.indices.breaker.HierarchyCircuitBreakerService.checkParentLimit(HierarchyCircuitBreakerService.java:342) ~[elasticsearch-7.4.0.jar:7.4.0]
        at org.elasticsearch.common.breaker.ChildMemoryCircuitBreaker.addEstimateBytesAndMaybeBreak(ChildMemoryCircuitBreaker.java:128) ~[elasticsearch-7.4.0.jar:7.4.0]
        at org.elasticsearch.transport.InboundHandler.handleRequest(InboundHandler.java:170) [elasticsearch-7.4.0.jar:7.4.0]
        at org.elasticsearch.transport.InboundHandler.messageReceived(InboundHandler.java:118) [elasticsearch-7.4.0.jar:7.4.0]

```

Edit: seems it might be backlogging logstash instances. Backlogging due to index template issues after index rollover last night, just fixed the templates and bouncing the logstash instances...

---

<div class="post-metadata">

**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\
**Post date:** [October 19, 2019, 1:17pm UTC](https://discuss.elastic.co/t/one-node-now-failing-after-successful-upgrade-6-8-7-4-day-before/204307/2 "2019-10-19T13:17:51Z")

</div>

fixing all template issues and bouncing all backlogged logstash instances and a full elastic cluster restart seems to have settled the issue for now 😅

---

<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:** [November 16, 2019, 1:17pm UTC](https://discuss.elastic.co/t/one-node-now-failing-after-successful-upgrade-6-8-7-4-day-before/204307/3 "2019-11-16T13:17:52Z")

</div>

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