Cannot install elasticsearch service on Windows 2012 R2 server

[mike-mosher]

Elasticsearch version: 5.0.0-rc1

Plugins installed: none

JVM version: jdk1.8.0_101

OS version: Windows 2012 R2 64-bit

Description of the problem including expected versus actual behavior:
Cannot install the service.

• I have the following environment variables set:
  • JAVA_HOME: C:\Program Files\Java\jdk1.8.0_101
  • ES_HEAP_SIZE: 8g
• I have verified that jvm.options have the following lines commented out:

## -Xms8g
## -Xmx8g

I run the following: .\elasticsearch-service.bat install elasticsearch-5.0.0-rc1

I get the following output:

Error: encountered environment variables that are no longer supported
Use jvm.options or ES_JAVA_OPTS to configure the JVM
ES_HEAP_SIZE=8g: set -Xms8g and -Xmx8g in jvm.options or add "-Xms8g -Xmx8g" to ES_JAVA_OPTS

I delete ES_HEAP_SIZE and add ES_JAVA_OPTS: "-Xms8g and -Xmx8g" (without quotes)

I run the command again and get the following:

Installing service      :  "elasticsearch-5.0.0-rc1"
Using JAVA_HOME (64-bit):  "C:\Program Files\Java\jdk1.8.0_101"
thread stack size not set; configure via C:\elasticsearch-5.0.0-rc1\config\jvm.options or ES_JAVA_OPTS

I delete ES_JAVA_OPTS and edit jvm.options:

-Xms8g
-Xmx8g

Run again and get the following:

Installing service      :  "elasticsearch-5.0.0-rc1"
Using JAVA_HOME (64-bit):  "C:\Program Files\Java\jdk1.8.0_101"
thread stack size not set; configure via C:\elasticsearch-5.0.0-rc1\config\jvm.options or ES_JAVA_OPTS

I leave jvm.options alone and create ES_JAVA_OPTS again. Now it see duplicate settings:

Installing service      :  "elasticsearch-5.0.0-rc1"
Using JAVA_HOME (64-bit):  "C:\Program Files\Java\jdk1.8.0_101"
duplicate min heap size settings found

[jasontedor]

You missed the message:

thread stack size not set; configure via C:\elasticsearch-5.0.0-rc1\config\jvm.options or ES_JAVA_OPTS

This is covered in the docs:

The service installer requires that the thread stack size setting be configured in jvm.options before you install the service. On 32-bit Windows, you should add -Xss320k to the jvm.options file, and on 64-bit Windows you should add -Xss1m to the jvm.options file.

Ideally you'll just set the heap and the stack size in the jvm.options file, leave ES_JAVA_OPTS out of it (it's there, it's an option, it's useful for development but the preferred approach is to just set your configs in the jvm.options file).

[jasontedor]

Many thanks for downloading and trying out 5.0.0-rc1; I've added you to the Pioneer Program. Please do let us know if you encounter any other issues. 😄

[mike-mosher]

I appreciate the help. I'm not a Java person, so I assumed it was barking about the heap size. I didn't realize there was a difference between this and the thread stack size.

Thanks for your help.

[jasontedor]

Thanks for your help.

You are very welcome.

[joniba]

@jasontedor the referenced docs do not contain the quoted paragraph about thread stack size. I think it's somewhat discouraging that non-java people running on windows need to sift through github issues just to try to start elastic for the very first time.

I'm sure it's all very clear to those that are fluent with the settings. But I don't even see this jvm.options file. I've read through the documentation about installing on windows and certainly it does not work as per the documentation (on windows 10 at least).

[jasontedor]

@joniba That's because we ship with thread stack size settings in the default jvm.options file now, you'll see this in the latest versions of the packages. Because of this, the note in question has been moved to a different page of the docs as it now pertains to all installations.

[jasontedor]

The point is, we recognize the pain that was here and are trying to make it easier.

Relates #21920

[joniba]

Sorry if I'm being a pain but the page you linked also does not mention setting -Xss1m in the jvm.options. I don't understand why there isn't a simple note somewhere, at least for windows users (or which ones need to set this? I didn't get it) to set this variable.

[jasontedor]

Sorry if I'm being a pain but the page you linked also does not mention setting -Xss1m in the jvm.options.

As I mentioned, you do not need to set it anymore with the default jvm.options file that ships with Elasticsearch starting in version 5.1.1 (the latest is 5.1.2). The note on the page that I linked to says:

Elasticsearch ships with default configuration for running Elasticsearch on 64-bit server JVMs. If you are using a 32-bit client JVM, you must remove -server from jvm.options and if you are using any 32-bit JVM you should reconfigure the thread stack size from -Xss1m to -Xss320k.

This is because the default jvm.options that we ship with works on all platforms except those that have a 32-bit client JVM (exceedingly rare these days). The stack size in the jvm.options also works on all platforms although it is best to change it on 32-bit JVMs.

[joniba]

Hmm I'm on 5.0.0 and getting the thread stack size error. I only downloaded it yesterday. Weird. Downloading 5.1.2 now.

[jasontedor]

Hmm I'm on 5.0.0 and getting the thread stack size error. I only downloaded it yesterday. Weird.

That's because the change to ship with a default was only introduced in 5.1.1.

Downloading 5.1.2 now.

You will not have this specific problem with that package.

[joniba]

Yes 5.1.2 worked more or less out of the box, thanks.