Cluster maintenance
Cluster maintenance includes...
- Applying fix packs and interim fixes
- Updating software release level on each node in the cluster
If you only have a vertical cluster, fixes requirng a restart will result in an outage for the end users.
Do not remove nodes from the cluster when applying fixes. Doing so may result in the inability to add the node back to the cluster.
Minor fixes
Minor fixes do not update the portal databases or require version upgrades. Use install instructions supplied with the fix.
Before applying, turn off the auto-synchronization. After deployment on all cluster nodes, force a manual synchronization, then re-enable auto-synchronization.
Fixes and service packs
The recommended approach is to install service packs using multiple production clusters...
- Modify the IP sprayer to remove a cluster from receiving user requests.
Allow time to finish handling existing user sessions
- Upgrade that cluster to install the service pack on all nodes
- After upgraded cluster is operational, it starts receiving production traffic while the next cluster is taken offline and goes through the upgrade process.
For environments with a single cluster...
- Remove a node or set of nodes from the flow of user traffic by configuring the IP sprayer and Web server.
- Upgrade the node with the service packs.
- After upgrading is complete, return the node or set of nodes to the flow of user traffic
- Repeat the repeating the procedure with the next node or set of nodes.
Related:
Set up a cluster on IBM i
Set up a cluster on AIX
Set up a cluster on Linux
Set up a cluster on Solaris
Set up a cluster on Windows