Upgrade Fusion 3.x to the newest release
The steps below describe how to upgrade Fusion 3.0 to the latest release. The
kazoo Python library must be installed before you begin.
Extract it to the same parent
fusionfolder as your earlier 3.0 release.
For example, if the fusion 3.0.0 is installed in
/opt/fusion/3.0.0, place the downloaded
fusion-3.0.1.tar.gzfile in the
/opt/folder and run:
tar zxvf fusion-3.0.1.tar.gz
FUSION_OLD_HOMEenvironment variable to the full path of the old version of the Fusion folder:
FUSION_HOMEenvironment variable to the full path of the new version of the Fusion folder:
Copy data from the old Fusion instance to the new instance:
cp -R $FUSION_OLD_HOME/data/ $FUSION_HOME/
Copy configurations from the old Fusion instance to the new instance:
mv $FUSION_HOME/conf/ $FUSION_HOME/conf_backup/ cp -R $FUSION_OLD_HOME/conf/ $FUSION_HOME/
If you are running distributed Fusion, then perform this step on all the Fusion nodes.Note
If you are running external Solr or Zookeeper, then modify the
fusion.propertiesto reflect the services that should be started when the
bin/fusionscript is executed.
Update links to point to the new Fusion instance:
cd $FUSION_HOME/.. unlink latest ln -s 3.0.1 latest
Start the Zookeeper server which will be used by the new Fusion installation.
If you are using the Zookeeper bundled within Fusion, that would be:
cd $FUSION_HOME ./bin/zookeeper start
Clone the fusion-upgrade-scripts repository, if you haven’t already:
git clone https://github.com/lucidworks/fusion-upgrade-scripts
Run the upgrade script:
cd fusion-upgrade-scripts/src python upgrade-3.0.x.py
Run the new version of Fusion (all services defined in
fusion.properties) and validate via the Fusion UI:
cd $FUSION_HOME ./bin/fusion startTip
Before accessing the Fusion UI, clear your browser’s cache. Otherwise, you may inadvertently access a cached version of the old Fusion UI and see inconsistent behavior.