Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

elasticsearch-service-x64 unable to reflect ES_HEAP_SIZE #3884

Closed
aamirmajeedkhan opened this Issue Oct 11, 2013 · 8 comments

Comments

Projects
None yet
2 participants
@aamirmajeedkhan
Copy link

commented Oct 11, 2013

Hi,
I am running elasticsearch 0.90.5 on windows 2008 R2. In service.bat I updated ES_HEAP_SIZE as 2g I checked script with Echo ON and it showed my 2g .
However when I run the service and check heap committed it comes as 111 mb .

I check running the es with elasticsearch.bat with ES_HEAP_SIZE=2g and it shows heap committed as 1.9 g.
By the way I am using server jre 1.7 u40 .
However I earlier tried client jre 1.7 u 25 but the result is same .

Thanks

@ghost ghost assigned costin Oct 13, 2013

@costin

This comment has been minimized.

Copy link
Member

commented Oct 13, 2013

Hi,

This is a duplicate of #3785 which has been fixed some time ago. Can you please try out the master/0.90 branch and let us know whether it works for you or not?

Thanks.

@costin costin closed this Oct 13, 2013

@aamirmajeedkhan

This comment has been minimized.

Copy link
Author

commented Oct 13, 2013

Hi,
It doesn't work as this time I recieved following message

call:convertxm 2g JVM_XMX
The system cannot find the batch label specified - convertxm

Thanks

@costin

This comment has been minimized.

Copy link
Member

commented Oct 13, 2013

Unfortunately I am unable to reproduce the problem. I am testing the latest 0.90 branch.
Here are the commands that I am running from the console from a Windows 7 x64 SP1:

> set ES_HEAP_SIZE=2g
> service install

Installing service      :  "elasticsearch-service-x64"
Using JAVA_HOME (64-bit):  "c:\jvm\jdk1.7"
The service 'elasticsearch-service-x64' has been installed.

> service manager

which displays the manager windows:
service-manager

Notice the Java tab which indicates the initial pool has been set to 2gb. I'm not sure what version you are using since by default, 1gb is used (which again shows up in the Java tab).

@aamirmajeedkhan

This comment has been minimized.

Copy link
Author

commented Oct 13, 2013

Hi,
Thanks for give it a try I am using Windows 2008 R2 . In my case it's not even writing anything in memory pool please have a look to attached snapshot
image

Interestingly service installed but because of missing memory value not able to start.
I believe that's happened because of failure of following statement in batch file
call convertxm %ES_MIN_MEM% JVM_XMS

I earlier tried 0.90.5 with NSSM - the Non-Sucking Service Manager and that seems to be working fine .
Since this is for live environment I am more inclined towards using 0.90.5 rather than latest build from github. What's your take on it .

Thanks

@costin

This comment has been minimized.

Copy link
Member

commented Oct 14, 2013

It looks like you are using the raw service.bat file from the trunk without having it build the project.
Can you please first build elasticsearch and then use the resulting file (from target/releases or target/bin)? Since otherwise the file is incomplete and results in an invalid build.

Try running mvn clean package -DskipTests and then looking at the relevant service.bat mentioned in the locations above. You can double check this by making sure no placeholders (${}) are used in your bat / settings.

@costin

This comment has been minimized.

Copy link
Member

commented Oct 14, 2013

One more thing - after updating the file, if it fails, can you run the bat as an administrator? Thanks.

@costin

This comment has been minimized.

Copy link
Member

commented Oct 14, 2013

Just tried the same ES configuration above (namely the master and trunk) on a fresh new install of Windows Server 2008 R2 x64 bits.
The service.bat installation works as expected - I've specified multiple combinations such as no environment variables, ES_MAX_SIZE and ES_HEAP_SIZE. For each I have changed the param, installed the service, removed the service.
P.S. I was running this from an administrator account (the default one)

@aamirmajeedkhan

This comment has been minimized.

Copy link
Author

commented Nov 7, 2013

I can confirm it fixed .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.