You can install Data Collector and start it manually or run it as a service.

You can install a full version of Data Collector that includes all stage libraries. Or, you can install a core version of Data Collector to install only the stage libraries that you want to use. The core installation allows Data Collector to use less disk space.

If you use Docker, you can also run the Data Collector image from Docker Hub.

If you use Cloudera Manager, you can install and administer Data Collector through Cloudera Manager.

Installation Requirements

Install Data Collector on a machine that meets the following minimum requirements. To run pipelines in cluster execution mode, each node in the cluster must meet the minimum requirements.

Component Minimum Requirement
Operating system Use one of the following operating systems and versions:
  • Mac OS X
  • CentOS 6 or 7
  • RedHat Enterprise Linux 6 or 7
  • Ubuntu 14.04 LTS or 16.04 LTS
Cores 2
Disk space 6 GB
File descriptors 32768
Java Oracle Java 8.
Note: OpenJDK is not supported.
Browser Use the latest version of one of the following browsers:
  • Chrome
  • Firefox
  • Safari

JCE for Oracle JVM

If you use AES-256 encryption with your Oracle JVM, install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy on the Data Collector machine.

For JCE installation instructions, see the README.txt file included in the jce_policy_x-zip file.

After the installation, restart Data Collector.

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, CentOS, and Ubuntu. However, refer to the administrator documentation for your operating system for the preferred method.

Increase the Limit on Mac OS

The method you use to increase the limit on Mac OS 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 Mac OS Yosemite, El Capitan, and Sierra:

  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" "">
    <plist version="1.0">
  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