Execution capacity

The Max. slots, Reserved slot %, and Max. memory properties control how the control plane assigns pipeline executions to nodes in the Snaplex. If all slots on a node are in use, new executions are sent to other nodes in the Snaplex, or held in a Queued state until resources become available.

Max. slots — Each Snap in a pipeline consumes one execution slot. Pipelines can only run on nodes where the number of slots in use is below this threshold; otherwise, normal pipeline executions fail or are placed in a Queued state depending on how they are invoked. For Ultra Task pipelines, the execution is queued. The number of slots in use corresponds to the number of active threads on the node, which you can view in the SnapLogic Monitor.

As a sizing heuristic, allocate 2000 slots per 8 GB of RAM on each node. For nodes with 16 GB of RAM, the default value of 4000 is appropriate. Changes to this setting do not require a restart.

Reserved slot % — Reserved slots are allocated for pipelines or validations executed interactively through the Designer — typically during development and testing. If no slots are reserved, interactive executions can be blocked by long-running pipelines. Pipelines started via Tasks or the Pipeline Execute Snap do not have access to reserved slots. Changes to this setting take effect immediately without a node restart. The default value is 15.

• Set the value higher to reserve more slots for interactive sessions.
• If interactive pipeline building is not a priority, set the value lower to allocate more capacity for automated executions.

Max. memory — When node memory usage reaches this threshold (expressed as a percentage of max heap), no additional pipelines are assigned to that node. Like Reserved slot %, this setting can be updated without restarting the node. The default value is 85.

Restart behavior

Max. restart wait time — The maximum time the monitor process waits before restarting an unresponsive node. Enabling the Set restart wait time to Forever toggle disables the numeric field and prevents automatic restarts. The default value is 15 minutes. Refer to Node initialization alerts for context on node restart scenarios.

Heap size

Max. heap size — Sets the maximum JVM heap size. The default value, auto, lets SnapLogic set the heap size automatically based on available machine memory. For details on auto-sizing tiers and swap memory configuration, refer to Memory management.

Network

HTTP Interface — Controls which network interface the node accepts connections on. Select Localhost only (127.0.0.1) to restrict connections to the local machine, or Any interface (0.0.0.0) to accept connections from any network interface. The default is Localhost only (127.0.0.1).

HTTP Port — The port on which the Snaplex node listens for HTTP connections. The default is 8090 for a JCC node and 8091 for a FeedMaster node.

HTTPS Port — The port on which the Snaplex node listens for HTTPS connections. No default value.

For firewall and port planning, refer to Groundplex requirements: Network.

Node configuration

Snaplex node types — Maps hostnames to node roles (JCC or FeedMaster). Additional entries can be added with + Add new node type.

Global properties — Key/value pairs for internal JVM and JCC configuration options. Do not edit these values without guidance from your CSM. Additional entries can be added with + Add new global property. For examples of common global property use cases, refer to Snaplex configuration for Snaps.