In a multi-node setup, an update job applies the update to nodes in the domain in a sequence. The sequence begins with the master gateway node. The Domain Management Service prepares the update plan that determines the sequence in which nodes are updated.
If you initiate the update, the Domain Management Service refreshes the update plan when you click Update. If you schedule the update to run at a later date and time, the Domain Management Service refreshes the update plan at the scheduled date and time. The plan includes all available nodes in the domain at the time it is refreshed. If the domain includes nodes that are offline when the update plan refreshes, they don't get included in the update plan. The update plan doesn't refresh after the update begins. Even if the node starts and becomes available, you can't include it in the update. You must manually update such nodes to ensure they are on the same version as other nodes in the domain. Contact Informatica Global Customer Support for information about how to manually update a node.
The update begins at the same time on all nodes in the domain. After download of binaries or the Prepare for update stage, the other nodes pause the update while the update continues on the master node. When the master node reaches the Clean-up stage, the other nodes continue the update and the update on these nodes progresses simultaneously. The update summary or status updates when the update is complete on all nodes in the domain update plan.
If the master node fails to start after the update is applied, a second gateway node becomes the master. However, the update job retains the initial master node information and waits for the node to start. The update therefore doesn't continue on other nodes until the initial master gateway node starts. Failure in other nodes doesn't impact the overall update job. If one node fails, the update continues on other nodes.