ECSAs can be disconnected from the Platform. This allows workflows and services to continue processing throughout the upgrade. The downtime of the workflows will be minimized to the restart of the Execution Contexts.
However, there are certain prerequisites that need to be fulfilled in order to do this:
- The traffic protocol must support failover.
- You cannot keep ECSAs running when there have been changes in the storage models for Aggregation, Inter Workflow, Usage Management, PCRF, or Routing Control. For information about changes in the storage models, see the Release Notes.
For more details about these prerequisites, see the System Administrator's Guide.
Hint!
You can use the Pico viewer in the Desktop or the configuration files in the directory $MZ_HOME/common/services/<ec name> on the Platform Container to find the EC/ECSAs that have installed services for ZooKeeper. You may also use the Java Monitoring and Management Console (JConsole) to see the current status of these services.
To disconnect the ECSAs, run the following command:
$ mzsh mzadmin/<password> disconnect <ecsa name> ...
Note!
Disconnected ECSAs may still attempt to contact the Platform. These attempts will fail and cause warning messages (No open connection to <Platform host> in the <ecsa-name>.log. Ignore these warning messages.