CircuitBreakingException internal:index/shard/recovery/start_recovery


(SK) #1

Hi All,

I am running a few nodes of ES 5.6.5 with HEAP set to 30G and indices.breaker.total.limit to 20% . Some of my shards are unassigned and i tried to restart and once the ES is started I still see some of the shards are getting unssigned. When I look into the reason of unassigned shards I get the below message

failed recovery, failure RecoveryFailedException[[.test_index][0]: Recovery failed from {WARM-10.0.4.205}{eBycpN86Tji7--R0uO5c4A}{JjnKxb6sSpyCQvEy81YOww}{10.0.4.205}{10.0.4.205:9300}{box_type=warm} into {WARM-10.0.4.214}{LG5CPCNaR4ycXdXUAlwZlQ}{TlPC7-Z7QdCkRsmANEQD3w}{10.0.4.214}{10.0.4.205:9300}{box_type=warm}]; nested: RemoteTransportException[[WARM-10.0.4.205][10.0.4.205:9300][internal:index/shard/recovery/start_recovery]]; nested: CircuitBreakingException[[parent] Data too large, data for [<transport_request>] would be [5594975772/5.2gb], which is larger than the limit of [5543336345/5.1gb]]; "

Is this issue due to indices.breaker.total.limit to 20% ?. Can you please suggest how I can look into this issue further


(system) #2

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