In this Article
| Table of Contents | ||||
|---|---|---|---|---|
|
Overview
Groundplex deployment comprises many factors for consideration. Most of these considerations are due to IT requirements in your computing environment, but some also depend on Pipeline production and the types of Pipelines you plan to run in production.
...
After the Snaplex service is started on a node, the service connects to the SnapLogic Cloud service. Runtime logs from the Snaplex are written to the /opt/snaplogic/run/log (or c:\opt\snaplogic\run\log) directory. The Dashboard shows the nodes that are currently connected for each Snaplex.
Snaplex Node Configuration
Snaplex nodes are typically configured using a slpropz configuration file, located in the $SL_ROOT/etc folder.
If you use the slpropz file as your Snaplex configuration, then:
After a Snaplex node is started with the
slpropzconfiguration, subsequent configuration updates are applied automatically.Changing the Snaplex properties in Manager causes each Snaplex node to download the updated
slpropzand initiates a rolling restart with no downtime on Snaplex instances with more than one node.Some configuration changes, such as an update to the logging properties does not require a restart and are applied immediately.
...
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.
...
You should always configure your Snaplex instances using the slpropz file because you do not have to edit the slpropz files manually and changes to the Snaplex done through Manager are applied automatically to all nodes in that Snaplex, making configuration issues, which may prevent the Snaplex from starting, automatically reverted.
Computing Requirements
The Groundplex must conform to the following minimum specifications:
...
Nodes (Min/Rec)
...
Minimum: 1
Recommended: 2 or more nodes
...
SnapLogic Project and Enterprise platform package nodes can be configured in the following sizes:
2 vCPU and 8GB RAM
4 vCPU and 16GB RAM
8 vCPU and 32GB RAM
16 vCPU and 64GB RAM
We recommend two nodes for high availability. For requirements about clustering nodes, see Node Cluster.
All nodes within a Snaplex must be of the same size.
...
RAM (Min)
...
Minimum: 8GB
...
Depending on the size, number, and nature of Pipelines, more RAM is required to maintain an acceptable level of performance.
...
CPU (Min)
...
Minimum: 2 core
...
All Snaps execute in parallel in their own threads: the more cores that are available to the Snaplex, the more performant the system.
...
JCC Node Communication within a Groundplex
We recommend that you set up JCC nodes in a Snaplex within the same network and data center. Communication between JCC nodes in the same Snaplex is required for the following reasons:
The Pipeline Execute Snap communicates directly with neighboring JCC nodes in a Snaplex to start child Pipeline executions and send documents between parent and child Pipelines.
The data displayed in Data Preview is written to and read from neighboring JCC nodes in the Snaplex.
The requests and responses made in Ultra Pipelines are exchanged between a FeedMaster node and all of the JCC nodes in a Snaplex.
A Ground Triggered Task (invoked from a Groundplex) can be executed on a neighboring JCC node due to load-balancing—in which case, the prepare request and the bodies of the request and response are transferred between nodes.
Therefore, any extra latency or network hops between neighboring JCC nodes can introduce performance and reliability problems.
Snaplex Node Configuration
Snaplex nodes are typically configured using a slpropz configuration file, located in the $SL_ROOT/etc folder.
If you use the slpropz file as your Snaplex configuration, then:
After a Snaplex node is started with the
slpropzconfiguration, subsequent configuration updates are applied automatically.Changing the Snaplex properties in Manager causes each Snaplex node to download the updated
slpropzand initiates a rolling restart with no downtime on Snaplex instances with more than one node.Some configuration changes, such as an update to the logging properties does not require a restart and are applied immediately.
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 |
You should always configure your Snaplex instances using the |
Computing Requirements
The Groundplex must conform to the following minimum specifications:
Nodes (Min/Rec) | Minimum: 40GB1 Recommended: 100GB | Local disk space is required for logging and for any Snap that uses the local disk for temporary storage (for example, Sort and Join Snaps). For details, see Temporary Folder. SnapLogic does not in anyway restrict the disk size of your Groundplex nodes. |
|---|
Memory (RAM) is used by the Pipelines to execute. Some Snaps, like Sort Snaps, which accumulate many documents, consume more memory; the amount of memory used is influenced by the volume and size of the documents being processed. For an optimum sizing analysis based on your requirements, contact your SnapLogic Sales Engineer.
Operating Systems
The SnapLogic on-premises Snaplex is supported on the following operating systems:
CentOS (or Red Hat) Linux 6.3 or newer.
Debian and Ubuntu Linux.
Windows Server 2008 64 bit, Windows Server 2012, and Windows Server 2016 with a minimum of 8GB RAM.
For improved security, the Groundplex machine timestamp is verified to check if it is in sync with the timestamp on the SnapLogic Cloud. Running a time service on the Groundplex node ensures that the timestamp is always kept in sync.
For Linux, see Basic NTP Configuration for more details on setting up a NTP server.
For Windows, see Windows Time Service Technical Reference for more information.
Large clock skew can also affect communication between the FeedMaster and the JCC nodes. The Date.now() expression language function might be different between Snaplex nodes, and Internal log messages might have skewed timestamps, making it more difficult to debug issues.
2 or more nodes | SnapLogic Project and Enterprise platform package nodes can be configured in the following sizes:
We recommend two nodes for high availability. For requirements about clustering nodes, see Node Cluster. All nodes within a Snaplex must be of the same size. | |
RAM (Min) | Minimum: 8GB | Depending on the size, number, and nature of Pipelines, more RAM is required to maintain an acceptable level of performance. |
|---|---|---|
CPU (Min) | Minimum: 2 core | All Snaps execute in parallel in their own threads: the more cores that are available to the Snaplex, the more performant the system. |
DISK (Min/Rec) | Minimum: 40GB Recommended: 100GB | Local disk space is required for logging and for any Snap that uses the local disk for temporary storage (for example, Sort and Join Snaps). For details, see Temporary Folder. SnapLogic does not in anyway restrict the disk size of your Groundplex nodes. |
Memory (RAM) is used by the Pipelines to execute. Some Snaps, like Sort Snaps, which accumulate many documents, consume more memory; the amount of memory used is influenced by the volume and size of the documents being processed. For an optimum sizing analysis based on your requirements, contact your SnapLogic Sales Engineer.
Operating Systems
The SnapLogic on-premises Snaplex is supported on the following operating systems:
CentOS (or Red Hat) Linux 6.3 or newer.
Debian and Ubuntu Linux.
Windows Server 2008 64 bit, Windows Server 2012, and Windows Server 2016 with a minimum of 8GB RAM.
For improved security, the Groundplex machine timestamp is verified to check if it is in sync with the timestamp on the SnapLogic Cloud. Running a time service on the Groundplex node ensures that the timestamp is always kept in sync.
For Linux, see Basic NTP Configuration for more details on setting up a NTP server.
For Windows, see Windows Time Service Technical Reference for more information.
Large clock skew can also affect communication between the FeedMaster and the JCC nodes. The Date.now() expression language function might be different between Snaplex nodes, and Internal log messages might have skewed timestamps, making it more difficult to debug issues.
Network Throughput Guidelines
...
in the etc/global.properties by adding it to the Update Snaplex dialog, Node Properties tab, Global properties table.
Best Practices for Setting Up JCC Node Intercommunication within a Groundplex
We recommend that you set up JCC nodes in a Snaplex within the same network and data center. Communication between JCC nodes in the same Snaplex is required for the following reasons:
The Pipeline Execute Snap communicates directly with neighboring JCC nodes in a Snaplex to start child Pipeline executions and send documents between parent and child Pipelines.
The data displayed in Data Preview is written to and read from neighboring JCC nodes in the Snaplex.
The requests and responses made in Ultra Pipelines are exchanged between a FeedMaster node and all of the JCC nodes in a Snaplex.
A Ground Triggered Task (invoked from a Groundplex) can be executed on a neighboring JCC node due to load-balancing—in which case, the prepare request and the bodies of the request and response are transferred between nodes.
Therefore, any extra latency or network hops between neighboring JCC nodes can introduce performance and reliability problems.
Load Balancer Guidelines
...