Use NSSM ( http://nssm.cc/ ) to create the service instead.
Organize your folders like this
C:\Elasticsearch\
C:\Elasticsearch\nssm.exe
C:\Elasticsearch\elasticsearch.bat
C:\Elasticsearch\elasticsearch-1.1.0\
C:\Elasticsearch\elasticsearch-1.2.2\
C:\Elasticsearch\data
C:\Elasticsearch\logs
The version is used not just in the title and description but also in the
starting script (to setup the classpath and such).
This is done on purpose, to make sure the incorrect version is not loaded by
accident (path rename, reinstall, etc...).
You could use sym links but then you'd have to
Would setting up a symbolic link still necessitate re-installing the
Windows service after each upgrade? I noticed that the service, when
installed, contains version-specific information in places such as the
display name and description.
IE:
Elasticsearch 1.4.1 (node-01)
Elasticsearch 1.4.1
Hi,
I'm a recent user of elasticsearch and was wondering what steps i should
take on upgrade to a newer version of elasticsearch on my windows server
2012?
I've installed elasticsearch as running service on windows with the
following commands: (3 nodes)
Hi,
Remove the old service (service remove) then install it again using the new
path.
Going forward you might want to look into using file-system links (which Windows Vista + supports) so that you can make
an alias
to the folder, install the service for it and reuse that across installs.
That
