# The write bulk is stuck for a long time, causing the node load to rise and the cluster cannot be written

**URL:** <https://discuss.elastic.co/t/the-write-bulk-is-stuck-for-a-long-time-causing-the-node-load-to-rise-and-the-cluster-cannot-be-written/151971>\
**Category:** Elasticsearch\
**Created:** [October 11, 2018, 5:37am UTC](https://discuss.elastic.co/t/the-write-bulk-is-stuck-for-a-long-time-causing-the-node-load-to-rise-and-the-cluster-cannot-be-written/151971 "2018-10-11T05:37:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![linyy](https://avatars.discourse-cdn.com/v4/letter/l/e36b37/32.png) [@linyy](https://discuss.elastic.co/u/linyy)\
**Post date:** [October 11, 2018, 5:37am UTC](https://discuss.elastic.co/t/the-write-bulk-is-stuck-for-a-long-time-causing-the-node-load-to-rise-and-the-cluster-cannot-be-written/151971/1 "2018-10-11T05:37:25Z")

</div>

Elasticsearch version: 6.4.1  
JVM version: openjdk 1.8.0\_45  
system: redhat 6.9

this task caused several nodes to load very high, and then the cluster could not write. Restart the node with high load to recover. Is there a solution? Thank you.

write tasks:  
indices:data/write/bulk[s] Hun4IlhdR3mxhGPFBMM5fQ:1818928909 Hun4IlhdR3mxhGPFBMM5fQ:1818928875 transport 1539219616118 09:00:16 25.1m

{  
"completed" : false,  
"task" : {  
"node" : "1Eb47iyTTYqO395zsINwlg",  
"id" : 4372465,  
"type" : "netty",  
"action" : "indices:data/write/bulk[s]",  
"status" : {  
"phase" : "waiting\_on\_primary"  
},  
"description" : "requests[6], index[excc]",  
"start\_time\_in\_millis" : 1539219706425,  
"running\_time\_in\_nanos" : 1742763237947,  
"cancellable" : false,  
"parent\_task\_id" : "GfSLSR-qRqW7ZPVS0Crqyg:288914124",  
"headers" : { }  
}  
}

node hot threads:  
::: {1.1.1.1\_hot}{mc0M2MimTBeLu8kyxvf5dw}{B0Sy-pRyTzul4TRfjlOcHA}{1.1.1.1}{1.1.1.1:9300}{ml.machine\_memory=405669679104, ml.max\_open\_jobs=20,

xpack.installed=true, box\_type=hot, ml.enabled=true}  
Hot threads at 2018-10-09T03:31:09.720, interval=500ms, busiestThreads=3, ignoreIdleThreads=true:

73.7% (368.7ms out of 500ms) cpu usage by thread 'elasticsearch[1.1.1.1\_hot][write][T#27]'  
5/10 snapshots sharing following 69 elements  
java.math.BigInteger.multiply(BigInteger.java:1512)  
java.math.BigInteger.multiplyToomCook3(BigInteger.java:1712)  
java.math.BigInteger.multiply(BigInteger.java:1512)  
java.math.BigInteger.multiplyToomCook3(BigInteger.java:1712)  
java.math.BigInteger.multiply(BigInteger.java:1512)  
java.math.BigInteger.multiplyToomCook3(BigInteger.java:1712)  
java.math.BigInteger.multiply(BigInteger.java:1512)  
java.math.BigInteger.multiplyToomCook3(BigInteger.java:1719)  
java.math.BigInteger.multiply(BigInteger.java:1512)  
java.math.BigInteger.multiplyToomCook3(BigInteger.java:1719)  
java.math.BigInteger.multiply(BigInteger.java:1512)  
java.math.BigInteger.multiplyToomCook3(BigInteger.java:1712)  
java.math.BigInteger.multiply(BigInteger.java:1512)  
java.math.BigInteger.pow(BigInteger.java:2302)  
java.math.BigDecimal.bigTenToThe(BigDecimal.java:3543)  
java.math.BigDecimal.bigMultiplyPowerTen(BigDecimal.java:3676)  
java.math.BigDecimal.setScale(BigDecimal.java:2445)  
java.math.BigDecimal.toBigInteger(BigDecimal.java:3025)  
org.elasticsearch.common.xcontent.support.AbstractXContentParser.toLong(AbstractXContentParser.java:195)  
org.elasticsearch.common.xcontent.support.AbstractXContentParser.longValue(AbstractXContentParser.java:220)  
org.elasticsearch.index.mapper.NumberFieldMapper$NumberType$7.parse(NumberFieldMapper.java:679)  
org.elasticsearch.index.mapper.NumberFieldMapper$NumberType$7.parse(NumberFieldMapper.java:655)  
org.elasticsearch.index.mapper.NumberFieldMapper.parseCreateField(NumberFieldMapper.java:1010)

---

<div class="post-metadata">

**Author:** ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)\
**Post date:** [October 11, 2018, 8:17am UTC](https://discuss.elastic.co/t/the-write-bulk-is-stuck-for-a-long-time-causing-the-node-load-to-rise-and-the-cluster-cannot-be-written/151971/2 "2018-10-11T08:17:19Z")

</div>

Do you have the document that is taking a long time to index?

You should be able to enable the indexing slowlog to log documents that are taking a long time to index:  
[https://www.elastic.co/guide/en/elasticsearch/reference/6.4/index-modules-slowlog.html#index-slow-log](https://www.elastic.co/guide/en/elasticsearch/reference/6.4/index-modules-slowlog.html#index-slow-log)

It looks like it's taking a long time in the parsing of the document, so I am curious what it looks like.

---

<div class="post-metadata">

**Author:** ![linyy](https://avatars.discourse-cdn.com/v4/letter/l/e36b37/32.png) [@linyy](https://discuss.elastic.co/u/linyy)\
**Post date:** [October 11, 2018, 1:04pm UTC](https://discuss.elastic.co/t/the-write-bulk-is-stuck-for-a-long-time-causing-the-node-load-to-rise-and-the-cluster-cannot-be-written/151971/3 "2018-10-11T13:04:28Z")

</div>

Thank you for your reply, there are a few 1s slow index, but there is no hot threads on this node.

---

<div class="post-metadata">

**Author:** ![linyy](https://avatars.discourse-cdn.com/v4/letter/l/e36b37/32.png) [@linyy](https://discuss.elastic.co/u/linyy)\
**Post date:** [October 18, 2018, 1:58am UTC](https://discuss.elastic.co/t/the-write-bulk-is-stuck-for-a-long-time-causing-the-node-load-to-rise-and-the-cluster-cannot-be-written/151971/4 "2018-10-18T01:58:37Z")

</div>

I modified this parameter to be changed to false

numeric\_detection

---

<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 15, 2018, 1:58am UTC](https://discuss.elastic.co/t/the-write-bulk-is-stuck-for-a-long-time-causing-the-node-load-to-rise-and-the-cluster-cannot-be-written/151971/5 "2018-11-15T01:58:41Z")

</div>

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