Page Comparison

In this Page

Table of Contents

maxLevel	2
absoluteUrl	true

...

Level

The logging level that log messages must meet to be captured in the main log file.

Select one of the following options:

Trace. Captures events at the most granular level, which is useful for deep analysis by developers.
Debug. Captures fine grained events and is typically used by Technical Support.
Info. Captures informational events that highlight the progress of the application.
Warning. Captures unexpected situations that might require attention.
Error. Captures error events that might still allow the application to continue running, but requires monitoring.

Note

title	Recommended Level

We recommend you use either Debug or Info logging levels to facilitate troubleshooting.

Log file size

The maximum log file size, given as a number with a unit. For example, 50 MB for 50 megabytes.

Main backup count

The number of backup log files to keep for the main log (jcc.json).

Error backup count

The number of backup log files to keep for the error log (jcc_error.json).

Access backup count

The number of backup log files to keep for the access log (jcc_access.json).

...

Maximum slots

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

Reserved slots %

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

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

Maximum memory %

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

Heap max size

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).

HTTP interface
Anchor
HTTP interface
HTTP interface

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)

HTTP port

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.

HTTPS port

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

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

Restart Max Wait Time

The maximum wait time before restarting a node. Enter the maximum wait time before restarting a node or click Forever for an infinite wait time.

Default: 15 minutes

Recommended. No greater than 60 minutes.

Note

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.

Snaplex node types:
Hostname/Server type pairs

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

Applicable in Ultra-enabled environments.

Global properties:
Key/Value pairs

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

...

Versions Compared

Old Version 81

New Version 82

Key