# It seemed to be stuck when initializing
**URL:** https://discuss.elastic.co/t/it-seemed-to-be-stuck-when-initializing/162191
**Category:** Elasticsearch
**Created:** [December 27, 2018, 2:51am UTC](https://discuss.elastic.co/t/it-seemed-to-be-stuck-when-initializing/162191 "2018-12-27T02:51:44Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@minhua1983](https://discuss.elastic.co/u/minhua1983)
#### Post date: [December 27, 2018, 2:51am UTC](https://discuss.elastic.co/t/it-seemed-to-be-stuck-when-initializing/162191/1 "2018-12-27T02:51:44Z")
It seems to be stuck when initializing.
I have no idea about why it happens when initializing.
What does elasticsearch do after the system distributes the heaps to elasticsearch?
Please check the text log below.
2018-12-26 13:42:38 Commons Daemon procrun stdout initialized
[2018-12-26T13:42:47,578][INFO][o.e.n.Node] [node-1] initializing ...
[2018-12-26T13:42:48,218][INFO][o.e.e.NodeEnvironment] [node-1] using [1] data paths, mounts [[(E:)]], net usable\_space [244.4gb], net total\_space [499.9gb], spins? [unknown], types [NTFS]
[2018-12-26T13:42:48,218][INFO][o.e.e.NodeEnvironment] [node-1] heap size [7.9gb], compressed ordinary object pointers [true]
2018-12-26 13:50:45 Commons Daemon procrun stdout initialized
[2018-12-26T13:50:48,117][INFO][o.e.n.Node] [node-1] initializing ...
[2018-12-26T13:50:48,226][INFO][o.e.e.NodeEnvironment] [node-1] using [1] data paths, mounts [[(E:)]], net usable\_space [244.4gb], net total\_space [499.9gb], spins? [unknown], types [NTFS]
[2018-12-26T13:50:48,226][INFO][o.e.e.NodeEnvironment] [node-1] heap size [7.9gb], compressed ordinary object pointers [true]
[2018-12-26T13:57:45,386][INFO][o.e.n.Node] [node-1] node name [node-1], node ID [z6ItgsQHTZe1gYx6sV-4ag]
[2018-12-26T13:57:45,386][INFO][o.e.n.Node] [node-1] version[5.6.4], pid[3724], build[8bbedf5/2017-10-31T18:55:38.105Z], OS[Windows Server 2008 R2/6.1/amd64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0\_172/25.172-b11]
[2018-12-26T13:57:45,386][INFO][o.e.n.Node] [node-1] JVM arguments [-Xms8g, -Xmx8g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -Djdk.io.permissionsUseCanonicalPath=true, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j.skipJansi=true, -XX:+HeapDumpOnOutOfMemoryError, -Delasticsearch, -Des.path.home=D:\elasticsearch-5.6.4, -Des.default.path.logs=D:\elasticsearch-5.6.4\logs, -Des.default.path.data=D:\elasticsearch-5.6.4\data, -Des.default.path.conf=D:\elasticsearch-5.6.4\config, exit, -Xms8192m, -Xmx8192m, -Xss1024k]
[2018-12-26T13:57:47,815][INFO][o.e.p.PluginsService] [node-1] loaded module [aggs-matrix-stats]
[2018-12-26T13:57:47,815][INFO][o.e.p.PluginsService] [node-1] loaded module [ingest-common]
[2018-12-26T13:57:47,815][INFO][o.e.p.PluginsService] [node-1] loaded module [lang-expression]
[2018-12-26T13:57:47,815][INFO][o.e.p.PluginsService] [node-1] loaded module [lang-groovy]
[2018-12-26T13:57:47,815][INFO][o.e.p.PluginsService] [node-1] loaded module [lang-mustache]
[2018-12-26T13:57:47,815][INFO][o.e.p.PluginsService] [node-1] loaded module [lang-painless]
[2018-12-26T13:57:47,815][INFO][o.e.p.PluginsService] [node-1] loaded module [parent-join]
[2018-12-26T13:57:47,815][INFO][o.e.p.PluginsService] [node-1] loaded module [percolator]
[2018-12-26T13:57:47,815][INFO][o.e.p.PluginsService] [node-1] loaded module [reindex]
[2018-12-26T13:57:47,815][INFO][o.e.p.PluginsService] [node-1] loaded module [transport-netty3]
[2018-12-26T13:57:47,815][INFO][o.e.p.PluginsService] [node-1] loaded module [transport-netty4]
[2018-12-26T13:57:47,815][INFO][o.e.p.PluginsService] [node-1] no plugins loaded
[2018-12-26T13:57:52,941][INFO][o.e.d.DiscoveryModule] [node-1] using discovery type [zen]
[2018-12-26T13:59:00,884][INFO][o.e.n.Node] [node-1] initialized
[2018-12-26T13:59:00,884][INFO][o.e.n.Node] [node-1] starting ...
[2018-12-26T13:59:01,695][INFO][o.e.t.TransportService] [node-1] publish\_address {10.111.12.100:9300}, bound\_addresses {[::]:9300}
[2018-12-26T13:59:01,727][INFO][o.e.b.BootstrapChecks] [node-1] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
[2018-12-26T13:59:04,832][INFO][o.e.c.s.ClusterService] [node-1] new\_master {node-1}{z6ItgsQHTZe1gYx6sV-4ag}{zthiQis5T9e5nytUQO2bkg}{10.111.12.100}{10.111.12.100:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)
[2018-12-26T13:59:04,926][INFO][o.e.h.n.Netty4HttpServerTransport] [node-1] publish\_address {10.111.12.100:9200}, bound\_addresses {[::]:9200}
[2018-12-26T13:59:04,926][INFO][o.e.n.Node] [node-1] started
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [December 27, 2018, 2:53am UTC](https://discuss.elastic.co/t/it-seemed-to-be-stuck-when-initializing/162191/2 "2018-12-27T02:53:28Z")
Please don't post pictures of text, they are difficult to read and some people may not be even able to see them 🙂
---
### Author:  [@minhua1983](https://discuss.elastic.co/u/minhua1983)
#### Post date: [December 29, 2018, 1:43am UTC](https://discuss.elastic.co/t/it-seemed-to-be-stuck-when-initializing/162191/3 "2018-12-29T01:43:17Z")
I have added the text log.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [January 2, 2019, 12:19am UTC](https://discuss.elastic.co/t/it-seemed-to-be-stuck-when-initializing/162191/4 "2019-01-02T00:19:27Z")
> [@minhua1983](#):
>
> [2018-12-26T13:50:48,226][INFO][o.e.e.NodeEnvironment] [node-1] heap size [7.9gb], compressed ordinary object pointers [true]
> [2018-12-26T13:57:45,386][INFO][o.e.n.Node] [node-1] node name [node-1], node ID [z6ItgsQHTZe1gYx6sV-4ag]
Are you saying it appears to be stuck based on these timestamps?
---
### Author:  [@minhua1983](https://discuss.elastic.co/u/minhua1983)
#### Post date: [January 3, 2019, 5:46am UTC](https://discuss.elastic.co/t/it-seemed-to-be-stuck-when-initializing/162191/5 "2019-01-03T05:46:59Z")
> [@minhua1983](#):
>
> 2-26T13:50:48,226][INFO][o.e.e.NodeEnvironment] [node-1] heap size [7.9gb], compressed ordinary object pointers [true]
> [2018-12-26T13:57:45,386][INFO][o.e.n.Node] [node-1] node name [node-1], node ID [z6ItgsQHTZe1gYx6sV-4ag]
Yes.
As usual, it will occur when the virtual machine restarts.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [January 3, 2019, 5:47am UTC](https://discuss.elastic.co/t/it-seemed-to-be-stuck-when-initializing/162191/6 "2019-01-03T05:47:55Z")
What is the system load like when that happens, do you have high CPU/disk/memory use?
---
### Author:  [@minhua1983](https://discuss.elastic.co/u/minhua1983)
#### Post date: [January 4, 2019, 2:52am UTC](https://discuss.elastic.co/t/it-seemed-to-be-stuck-when-initializing/162191/7 "2019-01-04T02:52:18Z")
The total memory size of virtual machine is 16 G.
The max memory size of elastic search is 8 G.
The initiative memory size of elastic search is 8 G.
The High CPU usage only happened after elastic search started to shard.The High CPU usage is between 50% and 80%.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 1, 2019, 2:54am UTC](https://discuss.elastic.co/t/it-seemed-to-be-stuck-when-initializing/162191/8 "2019-02-01T02:54:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.