Keep in mind the following upgrade considerations introduced in PingDirectory 9.x versions.
If you plan to upgrade servers using a mixed-version environment where one version is
earlier than 7.0 and some of the servers are still using the admin backend while
others have been updated to the topology registry, do not attempt to make size
changes to the topology. You cannot remove any existing servers (using
dsreplication disable
) or add new servers (using
dsreplication enable
) when in this transitional state of
partially-updated servers. When a topology has been completely migrated to a 7.0 or
later version with the topology registry, changes to the topology size are allowed,
even in mixed-version environments (for example, mixed 7.3 and 8.3).
Enabling replication-purge-obsolete-replicas
The following requirement applies when upgrading from a version earlier than 9.2 to version 9.2 or higher:
You must set the replication-purge-obsolete-replicas
global
configuration property to true
on each server in the topology
before beginning the upgrade process. Failure to do so could result in a server
entering lockdown mode over missing changes from an obsolete replica.
The following requirement applies when upgrading from a version earlier than 9.2 to version 9.2:
You must unset the target-database-size
configuration on any
nodes where it is set. When target-database-size
is set,
smaller obsolete replicas might not be purged, and this can cause the same
upgrade issues as when replication-purge-obsolete-replicas
is
set to false
.
Learn more about Purging obsolete replicas.
Cleaning replication history
When cleaning replication history from a PingDirectory server,
you must now use the new remove-defunct-server
argument
--performLocalCleanup
. If you have existing automation around
disaster recovery, the previous method of running
remove-defunct-server
without bind credentials no longer
performs this replication cleanup step. For PingDirectory versions 9.0.0.0 and later, update any
existing automation to use the --performLocalCleanup
flag.
Spring compatibility
Spring configuration properties in PingDirectory suite of products admin console configuration files before PingDirectory suite of products 9.0.0.0 are not compatible with the most recent admin console bundled with 9.0.0.0 and later versions of PingDirectory suite of products because of major updates to Spring dependencies. Attempting to use these older configuration files results in the console failing to start.
If you are using older PingDirectory suite of products admin console configuration files, update them by replacing the following excerpt in the old application.yml file:
spring:
profiles.active: default
main.show-banner: false
thymeleaf.cache: true
thymeleaf.prefix: classpath:/public/app/
with:
spring:
profiles.active: default
web.resources:
# 1 year. Update the corresponding value in MvcConfig if this changes.
cache.period: 31536000
add-mappings: false # use our custom mappings instead of the defaults
main:
banner-mode: "OFF"
thymeleaf:
prefix: classpath:/public/app/