After the Upgrade
Configure the upgraded instance
After the upgrade has been installed, browse to the Settings page of Dash Enterprise Server Manager and confirm your server is configured as desired. For more information, see Section 7.3: Basic settings.
Run the upgraded instance
After checking your configuration, click Save to start the new version.
Monitoring the upgrade
Upgrading Dash Enterprise can take anywhere between 20 minutes and two hours depending on the number of Dash apps & Workspaces on the platform and how long it takes for these apps to start. When Dash Enterprise is upgraded or restarted, all of the Dash Apps & Workspaces are rerun. To not overwhelm the server, Dash Enterprise restarts the services in batches, runs one service per CPU core. Also, when running more than four services in parallel, the Docker daemon itself has degraded performance and may further slow down this process.
Note that the UI in the Server Manager will display the application as being “Ready” before it is. This is a known bug. Instead, monitor the status of your upgrade by ssh
’ing into the host and running:
to view the status of apps being created. Check service and app restore operations:
If the upgrade gets stuck and the other logs don’t show anything useful:
These commands do not apply to Dash Enterprise Kubernetes.
Logs are buffered so you won’t see progress as the app is built, you will only see the logs once the app has finished building.
Known Upgrade Issues
If a Dash app fails to start, then the Dash Enterprise server can fail to restart. This is a bug and will be fixed in a future release. Detect that an app has failed to start by running this command:
If you see error messages like:
Then you can fix this issue by running:
Clean up after the upgrade
Once you are confident that the upgrade was successful, you may remove your backup with the following command:
There is no disadvantage associated with keeping the backup file as long as you have enough disk space.
Last updated