In this Article

Overview

You can configure properties for individual nodes in the Snaplex Properties tab. The first set of properties (Max slots, Reserved slots, and Max memory) affect how Pipeline executions are assigned to nodes in the Snaplex by the control plane. For example, if all of the slots on a node have been used for executing other Pipelines, any new executions are sent to other nodes in the Snaplex or the Control Plane keeps the Pipeline execution in a Queued state until resources become available.

Maximum Slots

Each Snap in a Pipeline consumes a slot, so Pipelines are only executed on nodes where the number of slots currently in use is below this threshold. Otherwise, the Pipelines fail or are placed in the Queued state, depending on how they are executed. The number of slots-in-use corresponds to the number of active threads on a node, which can be viewed on the Health tab on the SnapLogic Dashboard.

A heuristic to use is that 2000 slots can be allocated per 8GB of RAM available on each Snaplex node. So for nodes with 16GB of RAM, use 4000 (the default setting) as the slot count. A restart is not required with a change to this setting.

Reserved Slot Percentage

Reserved slots are allocated for Pipelines or validations that are executed manually from the SnapLogic Designer—typically used for testing or validation during development. If slots are not reserved, these interactive executions might be blocked by long-running Pipelines. Pipelines executed using Tasks or Pipeline Execute Snaps will not have access to these reserved slots.

You can adjust the number of reserved slots based on your needs.

• Set the value higher to reserve more slots for interactive sessions.

• Conversely, if interactive Pipeline building is not a priority for your Snaplex, you can set this value lower to allocate more capacity for automated executions.

Maximum memory percentage

You can also set the memory threshold at–and above–which no more Pipelines can be assigned to a node.