Upgrade from 2018.1
Follow these instructions to upgrade from 2018.1 to 2018.3.1.
You have to run the Promote upgrade script from a machine with SSH access to your Promote cluster.
Make sure these ports are open between nodes in your Promote cluster:
Make sure you walk through each of these steps before you run the 2018.1 upgrade script:
1. Update your R models to use jsonlite, instead of rjson.
The default JSON parser for R models has changed from rjson to jsonlite, which has slight parsing variations. If you think this may interfere with any of your R models, we recommend either of these options:
Modify and redeploy your model to Promote.
Create an environmental variable called
JSONLITE in the model. Assign to it the value
FALSE. This causes the model to revert back to rjson as its default parser. Follow these steps to modify a model you've deployed:
- Select the model inside the Promote UI.
- Select Advanced.
- Click the blue + under Environmental Variables.
- Enter the name
JSONLITEand the value
Open the upgrade script with a text editor (such as vi):
After you open the file, it should look like this:
- KEY_PATH='' # Path on local machine
Within each set of single quotation marks, use vi to insert this information:
- External IP addresses of the nodes that are already a part of your Promote cluster
- Internal IP addresses of the nodes that are already a part of your Promote cluster
- SSH user and key file
After you update the empty fields with needed information, the file should look like this:
- KEY_PATH='PATH/TO/SSH/KEY' # Path on local machine
Now that you've provided needed information to the upgrade script, run it:
The script prompts you to make a few selections. Confirm that all information is correct by providing either a y or n response to each prompt:
- Answer y to migrate Elasticsearch.
- Answer y to clean up old Promote instances.
- Answer y to configure Docker with the new 2018.3.1.
After you indicate your preferences by responding to those prompts, the script kicks off several upgrade actions on your nodes:
1. Your manager node performs these actions:
- Removes stale indexes and templates from Elasticsearch 5.x
- Stops Promote
- Waits about 10 seconds for Promote services to shut down
- Removes stale influxdb data
2. All nodes perform these actions:
- Update the daemon.json file for Docker and then restart it
- Update system logging settings to use journald and restart systemd-journald
- Replace the promote.yml compose file
- Replace the updateImages.py file
3. Promote then restarts, which triggers a redeploy of all models.
After the script completes, wait for Promote services to build the Promote UI and verify that it is up and running. You can watch these services generate:
Check the Promote UI to verify that it is running and that all your models successfully redeploy.
If a model fails to redeploy, select the Redeploy button in the UI to trigger a manual redeploy. Find the Redeploy button under the Advanced settings for your model. If a manual redeploy fails to resolve the problem, contact Alteryx Support.