This is driving me insane. I cannot work out why a fresh install of Java 1.8.0_121 and elasticsearch 5.2.1 is unable to start. I used elasticsearch 2.4 previously without issues, but have since removed it and tidied up my Java versions. Wanted to test out elasticsearch again, installed latest version and latest Java and just can't get it to start.
java -version
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) Client VM (build 25.121-b13, mixed mode)
javac -version
javac 1.8.0_121
echo %JAVA_HOME%
C:\Program Files (x86)\Java\jdk1.8.0_121
Given I am using the 32-bit JVM client I have removed -server from jvm.options and set the thread stack size to 320k.
From the elasticsearch service manager:
Java use default:
True
Java virtual machine:
c:\Program FIles (x86)\Java\jre.1.8.0_121\bin\client\jvm.dll
Java classpath:
c:\Workspace\ELK\elasticsearch-5.2.1/lib/elasticsearch-5.2.1.jar;c:\Workspace\ELK\elasticsearch-5.2.1/lib/*
Java options:
-Xms2g
-Xmx2g
-XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=75
-XX:+UseCMSInitiatingOccupancyOnly
-XX:+DisableExplicitGC
-XX:+AlwaysPreTouch
-Xss320k
-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=c:\Workspace\ELK\elasticsearch-5.2.1
-Des.default.path.logs=c:\Workspace\ELK\elasticsearch-5.2.1\logs
-Des.default.path.data=c:\Workspace\ELK\elasticsearch-5.2.1\data
-Des.default.path.conf=c:\Workspace\ELK\elasticsearch-5.2.1\config
Initial memory pool:
2048 MB
Maximum memory pool:
2048 MB
Thread stack size:
320 KB
What am I doing wrong/missing?
Cheers,
ATC