I am in the process of planning an upgrade from an Elastic Stack installed before my time. I've got all of the relevant upgrade docs (starting with the upgrade guide), but have a question about upgrading using the MSI when the previous install looks like it has used the unpacking a zip method.
When I run the 5.6 MSI installer it doesn't detect the previous install (5.3.2 - installation files in c:\elasticsearch and path.data/path.logs/path.repo in e:\elasticsearch), presumably because there are no reg keys set by an installer?
What I wanted to know was the optimal way to upgrade using MSI in this situation? Should I essentially treat it as a new install and migrate the indices data in and update config files or is there a way to get the MSI to detect the previous version?
Thanks in advance
I've been through an upgrade from zip install to MSI install in our Dev environment using the following process:
Stop then delete the Elasticsearch Windows service
Install Elasticsearch from MSI using all default directories but unchecking the option to start the service after install
Copy all defined values from the 'old' elasticsearch.yml into the newly generated one in c:\ProgramData\Elastic\config
Start the service
Not sure that this is the best way though and that I haven't missed anything so please do chime in if there are other considerations. For example I haven't worried about copying over anything in jvm.options because the MSI's defaults were fine
The process you describe sounds reasonable to me.
Thanks David, I appreciate the validation. Hopefully this will help anyone who comes across it as it doesn't appear to be covered in the MSI install KB - unless I have missed something
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.