For advanced use only, key-value pairs (one on each line) to be inserted into a role's environment. Applies to configurations of all
roles in this service except client configuration.

sqoop_env_safety_valve

false

Monitoring

Display Name

Description

Related Name

Default Value

API Name

Required

Enable Service Level Health Alerts

When set, Cloudera Manager will send alerts when the health of this service reaches the threshold specified by the EventServer
setting eventserver_health_events_alert_threshold

true

enable_alerts

false

Enable Configuration Change Alerts

When set, Cloudera Manager will send alerts when this entity's configuration changes.

false

enable_config_alerts

false

Service Triggers

The configured triggers for this service. This is a JSON formatted list of triggers. These triggers are evaluated as part as the
health system. Every trigger expression is parsed, and if the trigger condition is met, the list of actions provided in the trigger expression is executed. Each trigger has all of the following
fields:

triggerName(mandatory) - the name of the trigger. This value must be unique for the specific service.

streamThreshold(optional) - the maximum number of streams that can satisfy a condition of a trigger before the condition
fires. By default set to 0, and any stream returned causes the condition to fire.

enabled(optional) - by default set to 'true'. If set to 'false' the trigger will not be evaluated.

For example, here is a JSON formatted trigger that fires if there are more than 10 DataNodes with more than 500 file-descriptors opened:[{"triggerName": "sample-trigger",
"triggerExpression": "IF (SELECT fd_open WHERE roleType = DataNode and last(fd_open) > 500) DO health:bad", "streamThreshold": 10, "enabled": "true"}]Consult the trigger rules documentation
for more details on how to write triggers using tsquery.The JSON format is evolving and may change in the future and as a result backward compatibility is not guaranteed between releases at this
time.

sqoop2serverdefaultgroup

Advanced

For advanced use only, a string to be inserted into log4j.properties for this role only.

log4j_safety_valve

false

Heap Dump Directory

Path to directory where heap dumps are generated when java.lang.OutOfMemoryError error is thrown. This directory is automatically
created if it doesn't exist. However, if this directory already exists, role user must have write access to this directory. If this directory is shared amongst multiple roles, it should have 1777
permissions. Note that the heap dump files are created with 600 permissions and are owned by the role user. The amount of free space in this directory should be greater than the maximum Java Process
heap size configured for this role.

/tmp

oom_heap_dump_dir

false

Dump Heap When Out of Memory

When set, generates heap dump file when java.lang.OutOfMemoryError is thrown.

false

oom_heap_dump_enabled

true

Kill When Out of Memory

When set, a SIGKILL signal is sent to the role process when java.lang.OutOfMemoryError is thrown.

true

oom_sigkill_enabled

true

Automatically Restart Process

When set, this role's process is automatically (and transparently) restarted in the event of an unexpected failure.

For advanced use only, a string to be inserted into sqoop.properties for this role only.

sqoop_config_safety_valve

false

Java Configuration Options for Sqoop 2 Server

These arguments will be passed as part of the Java command line. Commonly, garbage collection flags or extra debugging flags would be
passed here.

sqoop_java_opts

false

Database

Display Name

Description

Related Name

Default Value

API Name

Required

Sqoop 2 Server Metastore Directory

Directory where the Sqoop 2 Server will place its metastore data.

/var/lib/sqoop2

sqoop_metastore_data_dir

true

Logs

Display Name

Description

Related Name

Default Value

API Name

Required

Sqoop 2 Server Logging Threshold

The minimum log level for Sqoop 2 Server logs

INFO

log_threshold

false

Sqoop 2 Server Maximum Log File Backups

The maximum number of rolled log files to keep for Sqoop 2 Server logs. Typically used by log4j.

10

max_log_backup_index

false

Sqoop 2 Server Max Log Size

The maximum size, in megabytes, per log file for Sqoop 2 Server logs. Typically used by log4j.

200 MiB

max_log_size

false

Monitoring

Display Name

Description

Related Name

Default Value

API Name

Required

Enable Health Alerts for this Role

When set, Cloudera Manager will send alerts when the health of this role reaches the threshold specified by the EventServer setting
eventserver_health_events_alert_threshold

true

enable_alerts

false

Enable Configuration Change Alerts

When set, Cloudera Manager will send alerts when this entity's configuration changes.

false

enable_config_alerts

false

Log Directory Free Space Monitoring Absolute Thresholds

The health test thresholds for monitoring of free space on the filesystem that contains this role's log directory.

Warning: 10 GiB, Critical: 5 GiB

log_directory_free_space_absolute_thresholds

false

Log Directory Free Space Monitoring Percentage Thresholds

The health test thresholds for monitoring of free space on the filesystem that contains this role's log directory. Specified as a
percentage of the capacity on that filesystem. This setting is not used if a Log Directory Free Space Monitoring Absolute Thresholds setting is configured.

Warning: Never, Critical: Never

log_directory_free_space_percentage_thresholds

false

Role Triggers

The configured triggers for this role. This is a JSON formatted list of triggers. These triggers are evaluated as part as the health
system. Every trigger expression is parsed, and if the trigger condition is met, the list of actions provided in the trigger expression is executed. Each trigger has all of the following fields:

triggerName(mandatory) - the name of the trigger. This value must be unique for the specific role.

streamThreshold(optional) - the maximum number of streams that can satisfy a condition of a trigger before the condition
fires. By default set to 0, and any stream returned causes the condition to fire.

enabled(optional) - by default set to 'true'. If set to 'false' the trigger will not be evaluated.

For example, here is a JSON formatted trigger configured for a DataNode that fires if the DataNode has more than 1500 file-descriptors opened:[{"triggerName":
"sample-trigger", "triggerExpression": "IF (SELECT fd_open WHERE roleName=$ROLENAME and last(fd_open) > 1500) DO health:bad", "streamThreshold": 0, "enabled": "true"}]Consult the trigger
rules documentation for more details on how to write triggers using tsquery.The JSON format is evolving and may change in the future and as a result backward compatibility is not guaranteed between
releases at this time.

[]

role_triggers

true

File Descriptor Monitoring Thresholds

The health test thresholds of the number of file descriptors used. Specified as a percentage of file descriptor limit.

Resource Management

Display Name

Description

Related Name

Default Value

API Name

Required

Cgroup CPU Shares

Number of CPU shares to assign to this role. The greater the number of shares, the larger the share of the host's CPUs that will be
given to this role when the host experiences CPU contention. Must be between 2 and 262144. Defaults to 1024 for processes not managed by Cloudera Manager.

cpu.shares

1024

rm_cpu_shares

true

Cgroup I/O Weight

Weight for the read I/O requests issued by this role. The greater the weight, the higher the priority of the requests when the host
experiences I/O contention. Must be between 100 and 1000. Defaults to 1000 for processes not managed by Cloudera Manager.

blkio.weight

500

rm_io_weight

true

Cgroup Memory Hard Limit

Hard memory limit to assign to this role, enforced by the Linux kernel. When the limit is reached, the kernel will reclaim pages
charged to the process. If reclaiming fails, the kernel may kill the process. Both anonymous as well as page cache pages contribute to the limit. Use a value of -1 B to specify no limit. By default
processes not managed by Cloudera Manager will have no limit.

memory.limit_in_bytes

-1 MiB

rm_memory_hard_limit

true

Cgroup Memory Soft Limit

Soft memory limit to assign to this role, enforced by the Linux kernel. When the limit is reached, the kernel will reclaim pages
charged to the process if and only if the host is facing memory pressure. If reclaiming fails, the kernel may kill the process. Both anonymous as well as page cache pages contribute to the limit. Use
a value of -1 B to specify no limit. By default processes not managed by Cloudera Manager will have no limit.

Stacks Collection

The amount of stacks data that will be retained. After the retention limit is reached, the oldest data will be deleted.

stacks_collection_data_retention

100 MiB

stacks_collection_data_retention

false

Stacks Collection Directory

The directory in which stacks logs will be placed. If not set, stacks will be logged into a stacks
subdirectory of the role's log directory.

stacks_collection_directory

stacks_collection_directory

false

Stacks Collection Enabled

Whether or not periodic stacks collection is enabled.

stacks_collection_enabled

false

stacks_collection_enabled

true

Stacks Collection Frequency

The frequency with which stacks will be collected.

stacks_collection_frequency

5.0 second(s)

stacks_collection_frequency

false

Stacks Collection Method

The method that will be used to collect stacks. The jstack option involves periodically running the jstack command against the
role's daemon process. The servlet method is available for those roles that have an HTTP server endpoint exposing the current stacks traces of all threads. When the servlet method is selected that
HTTP endpoint is periodically scraped.

If this documentation includes code, including but not limited to, code examples, Cloudera makes this available to you under the terms of the Apache License, Version 2.0, including any required
notices. A copy of the Apache License Version 2.0 can be found here.