Versions Compared

Old Version 5

changes.mady.by.user Chandna Mitra

Saved on

compared with

New Version 6

changes.mady.by.user John Brinckwirth

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The SnapLogic control plane and data plane were improved to more gracefully handle handles certain overload conditions on a Snaplex. This change introduces a new "Queued" , including a Queued state for pipeline executions and adds properties to the Snaplex configuration to set the resource thresholds used to detect an overload.Pipeline executions.  When an execution is in the Queued state, the control plane will try to start the execution when resources become available on the Snaplex.  You can also configure an Alert/Activity Notification for Snaplexes to set resource thresholds that detect congestion.


Note
  • A pipeline will Pipeline does not stay remain in the Queued state forever; it will timeout indefinitely and times out after a while. A scheduled pipeline will timeout Pipeline times out before the next scheduled execution or 4 hours, whichever comes first. A ForEach execution expires after 5 minutes. 
  • Not all methods of execution will result in a pipeline Pipeline being put into the Queued state. Only The Queued state applies only to executions started by a Scheduled Task or a ForEach Snap.

Pipeline executions started by the Designer will can fail immediately if the Snaplex is overloaded so that you are alerted of the overload; this condition triggers the alert notification if configured. Triggered Task executions will retry for a minute before returning a failure to the requesting client.

...