Basic upgrade

This guide discusses how to upgrade Deephaven on one or or more hosts. If your deployment uses Kubernetes, please refer to the Kubernetes upgrade guide. If your deployment uses Podman, consult the Podman upgrade guide.

Upgrading to Grizzly

As always, read the release notes and version log for any releases being skipped during this upgrade. If upgrading from Vermilion+ or earlier releases, review the release notes and version logs for all intermediate releases.

Critical breaking changes when upgrading to Grizzly:

  1. Java 8 support removed: The minimum required Java version is now 11, and version 17 is recommended. Legacy Java clients must use the same Java version as the server.

  2. Python 3.8 support removed: Grizzly supports Python 3.9 and 3.10 only.

  3. Manual iris-environment.prop changes required: Before upgrading, you must manually remove several legacy properties from your iris-environment.prop file. See the release notes for the complete list of properties to remove.

  4. Generated loggers must be regenerated: If you have generated loggers based on a previous version of Deephaven, you must regenerate them.

  5. In-Worker Service Persistent Query type removed: You must change the PQ type of any In-Worker Service PQs to Live Query - Merge Server.

  6. ACL storage default changed to etcd: Grizzly defaults to storing ACLs in etcd (DH_ACLS_USE_ETCD=true). If upgrading from a system using MySQL/MariaDB for ACLs:

    • The installer will create a fresh etcd ACL store with only the default iris account (with no password set).
    • You will not be able to log in after the upgrade until you migrate your ACL data or reconfigure to use MySQL.
    • Before upgrading, either:
      • Set DH_ACLS_USE_ETCD=false in your cluster.cnf to continue using MySQL ACLs, OR
      • Plan to migrate your ACL data after the upgrade using /usr/illumon/latest/bin/migrate_acls overwrite.
    • See Migrating ACLs to etcd for detailed migration instructions.

  7. Backup your data: Always ensure you have a complete backup of your data and configuration before upgrading.

  8. Test in a non-production environment: When possible, test the upgrade process in a development or staging environment before upgrading production systems.

For complete details on all breaking changes and new features, see the Grizzly release notes.

Upgrade process

To upgrade Deephaven to a newer version, update DH_VERSION to the desired version and re-run the process in the basic install document, replacing the installation media during the installation node setup.