Elasticsearch startup is waiting and takes 7 minutes to start

(Ben William) #1


I have a cluster with 2 nodes (another 1 will be added later). I made a fresh install. There is no data on ES. But on one node it takes 7 minutes to start. The system has 64GB ram but i can use with -Xms16g. If i set -Xms32g the system hangs and i wait 10 minutes, ES never start.

It is same on second node.

What can i do for this, any idea?

System Has 24 Core AMD CPU
64 GB Ram
Ubuntu 16.04 LTS
ES installed from apt repo.

Best Regards

(Christian Dahlqvist) #2

Is there anything in the Elasticsearch logs?

(Ben William) #3

Nothing on logs. After starting ES, it waits for 7-8 minutes (no logs for this time), then it is starting normally (after this point, logs are ok)

[2018-11-13T10:18:22,022][INFO ][o.e.x.m.j.p.NativeController] Native controller process has stopped - no new native processes can be star$
[2018-11-13T10:18:22,216][INFO ][o.e.n.Node ] [elastic1] stopped
[2018-11-13T10:18:22,216][INFO ][o.e.n.Node ] [elastic1] closing ...
[2018-11-13T10:18:22,270][INFO ][o.e.n.Node ] [elastic1] closed
[2018-11-13T10:27:03,964][INFO ][o.e.n.Node ] [elastic1] initializing ...
[2018-11-13T10:27:04,273][INFO ][o.e.e.NodeEnvironment ] [elastic1] using [1] data paths, mounts [[/var/lib/elasticsearch (/dev/vdb1)]]$
[2018-11-13T10:27:04,274][INFO ][o.e.e.NodeEnvironment ] [elastic1] heap size [15.8gb], compressed ordinary object pointers [true]
[2018-11-13T10:27:04,293][INFO ][o.e.n.Node ] [elastic1] node name [elastic1], node ID [dAFIwOd9RSyIaUbkFhePeA]

You can see after restart at 10:18, logs are started at 10:27.

(system) #4

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