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)
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 is, install under c:\elasticsearch\current (which can point to 1.1.0, then 1.1.1, 1.2.2, etc...) while your service
points to
\current.
Of course, you need to check whether each version introduces some changes into the init/stop script (does happen though
rarely)
and use that.
Cheers,
On 7/17/14 10:02 AM, Wesley Creteur wrote:
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)
|
C:\Elasticsearch\elasticsearch-1.1.0\bin\service install node-01
C:\Elasticsearch\elasticsearch-1.1.0\bin\service install node-02
C:\Elasticsearch\elasticsearch-1.1.0\bin\service install node-03
|
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 Windows Service - http://elasticsearch.org
Is there anything else (and possibly more important) that would make the
Windows service more version-specific and necessitate re-installing it
after every upgrade?
On Thursday, July 17, 2014 3:51:31 AM UTC-4, Costin Leau wrote:
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 is, install under c:\elasticsearch\current (which can point to 1.1.0,
then 1.1.1, 1.2.2, etc...) while your service
points to
\current.
Of course, you need to check whether each version introduces some changes
into the init/stop script (does happen though
rarely)
and use that.
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
C:\Elasticsearch....the other folders
in elasticsearch.bat only add the full path to the elasticsearch.bat that
is included with each version, for example
C:\Elasticsearch\elasticsearch-1.1.0\bin\elasticsearch.bat
Make sure your config has the folders C:\Elasticsearch\data defined
When upgrading, just add the new version in a folder, modify the bat in the
root and restart the service.
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 re-edit the startup scripts as well. It's simpler to reinstall the service:
service remove
service install
On 12/3/14 7:26 PM, Steve Camire wrote:
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 Windows Service - http://elasticsearch.org
Is there anything else (and possibly more important) that would make the Windows service more version-specific and
necessitate re-installing it after every upgrade?
On Thursday, July 17, 2014 3:51:31 AM UTC-4, Costin Leau wrote:
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 is, install under c:\elasticsearch\current (which can point to 1.1.0, then 1.1.1, 1.2.2, etc...) while your
service
points to
\current.
Of course, you need to check whether each version introduces some changes into the init/stop script (does happen though
rarely)
and use that.
Cheers,
--
Costin
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.