Page Comparison

The name of your Snaplex. Rename your Snaplex to provide a better description of the type or location. The name must not exceed 100 characters.

If you rename a Snaplex, then you must perform the following actions:

• Do a rolling restart on all the nodes in the Snaplex.

• Update any Pipe Execute Snaps that reference the old Snaplex name with the new name.

Uneditable. Indicates how the Snaplex is managed:

• Managed by SnapLogic: cloud

• Self-managed: sidekick

Enter the value used to configure the Snaplex nodes. Alphanumeric characters and the following special characters are allowed: . - +

Example: Dev-10

Default value: No default value

If you have an older Snaplex installation and its configuration is defined in the global.properties file, then the Environment value must match the jcc.environment value In the JCC global.properties file. To migrate your Snaplex configuration to the slpropz mechanism, see Migrating Older Snaplex Nodes.

The version of the Snaplex.

Update the version of your Snaplex by setting the Version in Manager. This manual update initiates a rolling restart of the nodes in the Snaplex. Each node is put offline with no new pipelines being sent to the node. The node waits a maximum of 15 minutes for currently running pipelines to finish and then restart itself with the new version of the Snaplex binaries. This process is repeated for each node. The Dashboard shows the updated nodes to be running with the new version.

Consider the following three designations when selecting the Snaplex version:

• Recommended. Indicates that this distribution is the version you should use.

• Restricted Distribution. Indicates that this version has a configuration intended for specific customers only.

• Deprecated. Indicates that this version is being phased out and should not be selected.

When you choose not to update your Snaplex manually and wait for the Automatic Update instead, you receive notifications until the Snaplex upgrade occurs. You can configure  your Snaplexes within an Org to update automatically in Manager when a new version is available.

Enter the email addresses for notification if one of the Snaplex nodes does not respond for fifteen minutes.

Enter the Slack channels, separated by commas, for notification if one of the Snaplex nodes does not respond for fifteen minutes.

Example: dev

Default value: None

Enter the Slack recipients, separated by commas, for notification if one of the Snaplex nodes does not respond for fifteen minutes.

Example: testuser

Default value: None

The URL for the load balancer for Triggered Task execution requests. The load balancer URL has to be fully qualified, including the protocol. 
When you save the Load balancer URLs in the Snaplex settings, these details are used for Snaplex Trigger URL.

Example: https://snaplexlb.mydomain.com

The URL for the FeedMaster load balancer for Ultra Pipeline execution requests.

This is available only to those Orgs subscribed to Ultra Pipeline Tasks.
Example: https://ultralb.mydomain.com

Description

The maximum number of slots available on each node in a Snaplex. Each Snap in a Pipeline will consume a slot, so Pipelines will only be executed on nodes where the number of slots currently in use is below this threshold. Otherwise, they will fail or be placed in the Queued state, depending on how they were executed. The number of slots-in-use corresponds to the number of active threads on a node, which can be viewed on the Monitoring Snaplex Health dashboard.

A restart is not required with a change to this setting, which can be set to a user-specified value.

Default value: 4000

The percentage of slots to reserve on a node for pipelines executed through the Designer tab. A restart is not required with a change to this setting.

Default value: 15

Pipelines executed using Tasks or the ForEach Snap do not have access to these slots.

The threshold at which no more pipelines will be assigned to a node.

A restart is not required with a change to this setting.

Default value: 85

Groundplex only. The maximum JVM heap size.

Default value: auto (meaning that SnapLogic will automatically set the max heap size based on the available machine memory).

Groundplex only. Choose where the Snaplex node will accept HTTP network connections from. Options include:

• Localhost only (127.0.0.1)

• Any interface (0.0.0.0)

Groundplex only. The HTTP port the Snaplex node will listen on for connections.

Default Values: 8090 for a JCC node and 8091 for a FeedMaster.

Groundplex only. The HTTPS port the Snaplex node will listen on for connections. 

Default Values: 8081 for a JCC node and 8084 for a FeedMaster.

The maximum wait time before restarting a node.

Enter the maximum wait time or click Forever for an infinite wait time. When a Snaplex node goes into Maintenance mode or a Cooldown state, any Pipeline executions exceeding this value will cause those Pipelines to fail.

Learn more about the Snaplex states.

Default: 15 minutes

Recommended. No greater than 60 minutes.

We recommend that you avoid setting the Restart Max Wait Time for too long because Snaplex nodes on an older version will stop accepting new Pipeline execution requests after the mandatory upgrade. This scenario can cause the nodes to wait for running Pipelines to complete and new Pipeline executions to not start as the older Snaplex version is no longer supported. The automatic Snaplex update has a 60-minute window during which the older version is supported. 

Groundplex only. Specify the type of service a Snaplex node should provide.

Applicable in Ultra-enabled environments.

Groundplex only. Internal configuration options. Do not edit these values without contacting SnapLogic Customer Support.