Requirements for Self-Managed Deployments

When working with self-managed deployments, you take full control of procuring the resources needed to run a Data Collector engine. You must set up the machine and complete the installation prerequisites required by the engine.

Before launching a Data Collector engine for a self-managed deployment, set up a machine with the following minimum requirements. Then, complete the additional Docker image prerequisites or tarball prerequisites based on the installation type you want to use.

Component Minimum Requirement
Operating system Use one of the following operating systems and versions:
  • Mac OS X
  • Amazon Linux 2
  • CentOS 6.x or 7.x
  • Oracle Linux 6.x - 8.x
  • Red Hat Enterprise Linux 6.x - 8.x
  • Ubuntu 14.04 LTS - 20.04 LTS
Cores 2
RAM 1 GB
Disk space 6 GB
Note: StreamSets does not recommend using NFS or NAS to store Data Collector files.

Docker Image Prerequisites

For a Docker image installation of Data Collector, the machine must also have Docker installed.

Tarball Prerequisites

For a tarball installation of Data Collector, the machine must meet the following additional minimum requirements:

Component Minimum Requirement
File descriptors 32768
Java
One of the following Java versions:

Some Data Collector functionality is dependent on the Java version that you use. For more information, see Java Versions and Available Features.

Java Versions and Available Features

The Java version installed on the Data Collector machine determines the Data Collector features that you can use.

All supported Java versions provide almost all Data Collector features. However due to third-party requirements, some features require a particular Java version. For example, MapR 7.0.x requires Java JDK 11 or higher, so you must use Java 11 or 17 to work with MapR 7.0.x stages.

The following table describes the features available with different Java versions:
Java Version Unavailable Features
Java 8 (Oracle Java 8 and Open JDK 8) Provides access to all Data Collector features except for the following:
  • Stages in the MapR 7.0.x stage library
Java 11 (Oracle Java 11 and Open JDK 11)

Java 17 (Oracle Java 17 and Open JDK 17)

Provides access to all Data Collector features except for the following:
  • Stages in MapR stage libraries earlier than 7.0.x

JCE for Oracle JVM

If you use AES-256 encryption with your Oracle JVM and use a version of JDK earlier than 1.8.0_161, then configure the JDK on the Data Collector machine to use the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy.

To configure the JDK to use unlimited cryptography, set the crypto.policy Java Security property in the java.security file included in your JDK installation to a value of unlimited. See the notes in the java.security file for more information.

Configuring the Open File Limit

Data Collector requires a large number of file descriptors to work correctly with all stages. Most operating systems provide a configuration to limit the number of files a process or a user can open. The default values are usually less than the Data Collector requirement of 32768 file descriptors.

Use the following command to verify the configured limit for the current user:
ulimit -n

Most operating systems use two ways of configuring the maximum number of open files - the soft limit and the hard limit. The hard limit is set by the system administrator. The soft limit can be set by the user, but only up to the hard limit.

Increasing the open file limit differs for each operating system. Consult your operating system documentation for the preferred method.

Increase the Limit on Linux

To increase the open file limit on Linux, see the following solution: How to set ulimit values.

This solution should work on Red Hat Enterprise Linux, Oracle Linux, CentOS, and Ubuntu. However, refer to the administrator documentation for your operating system for the preferred method.

Increase the Limit on MacOS

The method you use to increase the limit on MacOS can differ with each version. Refer to the documentation for your operating system version for the preferred method.

To increase the limit for the computer - so that the limits are retained after relaunching the terminal and restarting the computer - create a property list file. The following steps are valid for recent MacOS versions:

  1. Use the following command to create a property list file named limit.maxfiles.plist:
    sudo vim /Library/LaunchDaemons/limit.maxfiles.plist
  2. Add the following contents to the file, modifying the maxfiles attribute as needed.

    The maxfiles attribute defines the open file limit. The first value in the file is the soft limit. The second value is the hard limit.

    For example, in the following limit.maxfiles.plist file, both the soft and hard limit are set to 32,768:

    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
      <dict>
        <key>Label</key>
        <string>limit.maxfiles</string>
        <key>ProgramArguments</key>
        <array>
          <string>launchctl</string>
          <string>limit</string>
          <string>maxfiles</string>
          <string>32768</string>
          <string>32768</string>
        </array>
        <key>RunAtLoad</key>
        <true/>
        <key>ServiceIPC</key>
        <false/>
      </dict>
    </plist>
  3. Use the following commands to load the new settings:
    sudo launchctl unload -w /Library/LaunchDaemons/limit.maxfiles.plist
    sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist
  4. Use the following command to check that the system limits were modified:
    launchctl limit maxfiles
  5. Use the following command to set the session limit:
    ulimit -n 32768