It seemed to be stuck when initializing

minhua1983 · December 27, 2018, 2:51am

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 [2018-12-26T13:50:48,117][INFO ][o.e.n.Node [2018-12-26T13:50:48,226][INFO ][o.e.e.NodeEnvironment [2018-12-26T13:50:48,226][INFO ][o.e.e.NodeEnvironment [2018-12-26T13:57:45,386][INFO ][o.e.n.Node [2018-12-26T13:57:45,386][INFO ][o.e.n.Node [2018-12-26T13:57:45,386][INFO ][o.e.n.Node [2018-12-26T13:57:47,815][INFO ][o.e.p.PluginsService [2018-12-26T13:57:47,815][INFO ][o.e.p.PluginsService [2018-12-26T13:57:47,815][INFO ][o.e.p.PluginsService [2018-12-26T13:57:47,815][INFO ][o.e.p.PluginsService [2018-12-26T13:57:47,815][INFO ][o.e.p.PluginsService [2018-12-26T13:57:47,815][INFO ][o.e.p.PluginsService [2018-12-26T13:57:47,815][INFO ][o.e.p.PluginsService [2018-12-26T13:57:47,815][INFO ][o.e.p.PluginsService [2018-12-26T13:57:47,815][INFO ][o.e.p.PluginsService [2018-12-26T13:57:47,815][INFO ][o.e.p.PluginsService [2018-12-26T13:57:47,815][INFO ][o.e.p.PluginsService [2018-12-26T13:57:47,815][INFO ][o.e.p.PluginsService [2018-12-26T13:57:52,941][INFO ][o.e.d.DiscoveryModule [2018-12-26T13:59:00,884][INFO ][o.e.n.Node [2018-12-26T13:59:00,884][INFO ][o.e.n.Node [2018-12-26T13:59:01,695][INFO ][o.e.t.TransportService [2018-12-26T13:59:01,727][INFO ][o.e.b.BootstrapChecks [2018-12-26T13:59:04,832][INFO ][o.e.c.s.ClusterService [2018-12-26T13:59:04,926][INFO ][o.e.h.n.Netty4HttpSe [2018-12-26T13:59:04,926][INFO ][o.e.n.Node initialized
] [node-1] initializing ...
] [node-1] using [1] data paths, mounts [[(E:)]], net usable_space [244.4gb], net total_space [499.9gb], spins? [unknown], types [NTFS]
] [node-1] heap size [7.9gb], compressed ordinary object pointers [true]
] [node-1] node name [node-1], node ID [z6ItgsQHTZe1gYx6sV-4ag]
] [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]
] [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]
] [node-1] loaded module [aggs-matrix-stats]
] [node-1] loaded module [ingest-common]
] [node-1] loaded module [lang-expression]
] [node-1] loaded module [lang-groovy]
] [node-1] loaded module [lang-mustache]
] [node-1] loaded module [lang-painless]
] [node-1] loaded module [parent-join]
] [node-1] loaded module [percolator]
] [node-1] loaded module [reindex]
] [node-1] loaded module [transport-netty3]
] [node-1] loaded module [transport-netty4]
] [node-1] no plugins loaded
] [node-1] using discovery type [zen]
] [node-1] initialized
] [node-1] starting ...
] [node-1] publish_address {10.111.12.100:9300}, bound_addresses {[::]:9300}
] [node-1] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
] [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)
rverTransport] [node-1] publish_address {10.111.12.100:9200}, bound_addresses {[::]:9200}
] [node-1] started

warkolm · December 27, 2018, 2:53am

Please don't post pictures of text, they are difficult to read and some people may not be even able to see them

minhua1983 · December 29, 2018, 1:43am

I have added the text log.

warkolm · January 2, 2019, 12:19am

Are you saying it appears to be stuck based on these timestamps?

minhua1983 · January 3, 2019, 5:46am

Yes.
As usual, it will occur when the virtual machine restarts.

warkolm · January 3, 2019, 5:47am

What is the system load like when that happens, do you have high CPU/disk/memory use?

minhua1983 · January 4, 2019, 2:52am

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%.

system · February 1, 2019, 2:54am

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