...
A state transition can occur for many reasons–because of a Snaplex version update, a configuration change to the Snaplex, or a restart. When a state transition is required for a Snaplex, one node (or more for larger Snaplex instances) at a time enters a Cooldown state, in which new Pipeline execution requests are should not be not sent to the node. In this state, the node waits for currently running Pipelines to complete. For long-running Pipelines that are set up to poll continuously (like a Pipeline using File Poller or JMS Consumer Snaps) and Ultra Pipelines, the Pipeline is sent a state notification to allow the Pipeline to stop polling for new records.
| Info |
|---|
In the Cooldown state, a node can only accept requests if sent by the client directly. |
Pipeline Execution Timeout when Restarting a Snaplex
A node can stay in the Cooldown state for Snaplex has a configurable timeout (the default is 15 minutes), called the Restart Max Wait Time, which you can set in the Snaplex Settings tab in the Update Snaplex and Create Snaplex dialogs. If all Pipelines complete within this timeout, then the node transitions to the required state. If Pipelines are still running after this timeout, then those Pipelines terminate to allow the transition to the required state.
...
We strongly recommend that you keep the Restart Max Wait Time below one hour. Setting a larger timeout can cause issues because configuration and version changes take a longer time to apply. During the final Snaplex version upgrade (four weeks after the release involving the Snaplex upgrade), the SnapLogic control plane waits one hour for all Snaplex instances still on the older version to upgrade to the new version. Beyond one hour, the control plane does not allow new Pipeline execution requests on the old version.
If you use the Snaplex for Triggered Pipeline or Ultra Pipeline executions, we strongly recommend you to setup a load balancer on the Snaplex configured to use a /wiki/spaces/DRWIP/pages/2553513070 health check on the node state. Without a properly configured load balance, requests would continue to come to the node while in Cooldown state, causing failures.
You can set the timeout to Forever, which would never allow the Snaplex to go into a transition state. However, setting the timeout to Forever places the onus of manual termination of Pipelines on the Org admin. Essentially, you would need to terminate some Pipelines manually to force a state transition in the Snaplex.
If you decrease the timeout to an extremely low value like 2, then any Pipeline of a longer duration is terminated before completion.
...
When you place a Snaplex node in maintenance mode, the node enters the Cooldown state and waits for running Pipelines to complete. After all Pipelines completePipeline runs come to completion, the node enters maintenance mode, during which the node does not accept any Pipeline execution requests.
...
Groundplex: If a node is in maintenance mode and the Snaplex version is updated, the Groundplex remains in the maintenance mode after the update.
...