WARN Clear SC failed on node

2022-09-21T04:25:34+02:00 {"type": "server", "timestamp": "2022-09-21T02:25:34,358Z", "level": "WARN", "component": "o.e.a.s.TransportClearScrollAction", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-1", "message": "Clear SC failed on node[{elasticsearch-master-0}{R8X3DL8_R22p0tlev4Jkog}{-Vt6UavYRG-3NabfxBdsDg}{10.12.17.235}{10.12.17.235:9300}{dilmrt}{ml.machine_memory=2684354560, ml.max_open_jobs=20, xpack.installed=true, transform.node=true}]", "cluster.uuid": "uuiduuid123454646", "node.id": "xxxxx2435Xq_lo-XQ" , 

2022-09-21T04:25:34+02:00 "Caused by: org.elasticsearch.common.breaker.CircuitBreakingException: [parent] Data too large, data for [indices:data/read/search[free_context/scroll]] would be [1278122708/1.1gb], which is larger than the limit of [1245184000/1.1gb], real usage: [1278122648/1.1gb], new bytes reserved: [60/60b], usages [request=198852608/189.6mb, fielddata=0/0b, in_flight_requests=60/60b, accounting=1146098/1mb]"

Related

• Data too large, data for
• Elasticsearch index

See also

• Elasticsearch, installation, ELK, Elastic X-Pack, elasticsearch.yml, logs, ECK, Elasticsearch curl URLs, Elastisearch REST APIs, /_cat/, /_cluster/, /_xpack/, QueryShardException, Elasticsearch index, ELK backup and restore, elasticsearch-cli, Elasticsearch versions, ElasticSearch Snapshot Lifecycle Management (SLM), Low disk watermark, Elasticsearch storage, Elasticsearch users, Elasticsearch roles, search context, shards, Elastic Cloud, Elastic Licensing, ElasticSearch alerts