Impala Properties in CDH 5.0.0

Role groups:

impalacatalogserverdefaultgroup

Advanced

Display Name Description Related Name Default Value API Name Required
Catalog Server Command Line Argument Advanced Configuration Snippet (Safety Valve) For advanced use only, key-value pairs (one on each line) to be added (verbatim) to Catalog Server command line flags. Key names should begin with a hyphen(-). For example: -log_filename=foo.log catalogd_cmd_args_safety_valve false
Catalog Server HBase Advanced Configuration Snippet (Safety Valve) For advanced use only, a string to be inserted into hbase-site.xml for this role only. catalogd_hbase_conf_safety_valve false
Catalog Server HDFS Advanced Configuration Snippet (Safety Valve) For advanced use only, a string to be inserted into hdfs-site.xml for this role only. catalogd_hdfs_site_conf_safety_valve false
Catalog Server Hive Advanced Configuration Snippet (Safety Valve) For advanced use only, a string to be inserted into hive-site.xml for this role only. catalogd_hive_conf_safety_valve false
Catalog Server Hive Metastore Connection Timeout Timeout for requests to the Hive Metastore Server from Catalog Server. Consider increasing this if you have tables with a lot of metadata and see timeout errors. hive.metastore.client.socket.timeout 1 hour(s) hive_metastore_timeout false
Automatically Restart Process When set, this role's process is automatically (and transparently) restarted in the event of an unexpected failure. true process_auto_restart true

Logs

Display Name Description Related Name Default Value API Name Required
Catalog Server Log Directory Directory where Catalog Server will place its log files. log_dir /var/log/catalogd log_dir false
Impala Catalog Server Logging Threshold The minimum log level for Impala Catalog Server logs INFO log_threshold false
Catalog Server Verbose Log Level Verbose logging level for the GLog logger. These messages are always logged at 'INFO' log level, so this setting has no effect if Logging Threshold is set to 'WARN' or above. GLOG_v 1 log_verbose_level false
Catalog Server Log Buffer Level Buffer log messages logged at this level or lower (-1 means don't buffer; 0 means buffer INFO only; 1 means buffer WARNING only, ...) logbuflevel 0 logbuflevel false
Impala Catalog Server Max Log Size The maximum size, in megabytes, per log file for Impala Catalog Server logs. Typically used by log4j. 200 MiB max_log_size false

Monitoring

Display Name Description Related Name Default Value API Name Required
Catalog Server Connectivity Health Test Enables the health test that verifies the Catalog Server is connected to the StateStore true catalogserver_connectivity_health_enabled false
Catalog Server Connectivity Tolerance at Startup The amount of time to wait for the Catalog Server to fully start up and connect to the StateStore before enforcing the connectivity check. 3 minute(s) catalogserver_connectivity_tolerance false
File Descriptor Monitoring Thresholds The health test thresholds of the number of file descriptors used. Specified as a percentage of file descriptor limit. Warning: 50.0 %, Critical: 70.0 % catalogserver_fd_thresholds false
Impala Catalog Server Host Health Test When computing the overall Impala Catalog Server health, consider the host's health. true catalogserver_host_health_enabled false
Impala Catalog Server Process Health Test Enables the health test that the Impala Catalog Server's process state is consistent with the role configuration true catalogserver_scm_health_enabled false
Health Check Startup Tolerance The amount of time allowed after this role is started that failures of health checks that rely on communication with this role will be tolerated. 5 minute(s) catalogserver_startup_tolerance false
Web Metric Collection Enables the health test that the Cloudera Manager Agent can successfully contact and gather metrics from the web server. true catalogserver_web_metric_collection_enabled false
Web Metric Collection Duration The health test thresholds on the duration of the metrics request to the web server. Warning: 10 second(s), Critical: Never catalogserver_web_metric_collection_thresholds false
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
Resident Set Size Thresholds The health test thresholds on the resident size of the process. Warning: Never, Critical: Never process_resident_set_size_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.
  • triggerExpression (mandatory) - a tsquery expression representing the trigger.
  • 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
Unexpected Exits Thresholds The health test thresholds for unexpected exits encountered within a recent period specified by the unexpected_exits_window configuration for the role. Warning: Never, Critical: Any unexpected_exits_thresholds false
Unexpected Exits Monitoring Period The period to review when computing unexpected exits. 5 minute(s) unexpected_exits_window false

Other

Display Name Description Related Name Default Value API Name Required
Enable Catalog Server Web Server Enable/Disable Catalog Server web server. This web server contains useful information about Catalog Server daemon. enable_webserver true catalogd_enable_webserver false

Performance

Display Name Description Related Name Default Value API Name Required
Maximum Process File Descriptors If configured, overrides the process soft and hard rlimits (also called ulimits) for file descriptors to the configured value. rlimit_fds false

Ports and Addresses

Display Name Description Related Name Default Value API Name Required
Catalog Server Service Port Port where Catalog Server is exported. catalog_service_port 26000 catalog_service_port false
Catalog Server HTTP Server Port Port where Catalog Server debug web server runs. webserver_port 25020 catalogserver_webserver_port false

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. memory.soft_limit_in_bytes -1 MiB rm_memory_soft_limit true

Security

Display Name Description Related Name Default Value API Name Required
SSL Certificate File Location The location of the debug web server's SSL certificate file, in .pem format. If empty, webserver SSL support is not enabled. webserver_certificate_file webserver_certificate_file false
Catalog Server Web Server User Password Password for Catalog Server web server authentication. webserver_htpassword_password webserver_htpassword_password false
Catalog Server Web Server Username Username for Catalog Server web server authentication. webserver_htpassword_user webserver_htpassword_user false

impaladaemondefaultgroup

Advanced

Display Name Description Related Name Default Value API Name Required
Impala Daemon Hive Metastore Connection Timeout Timeout for requests to the Hive Metastore Server from Impala. Consider increasing this if you have tables with a lot of metadata and see timeout errors. hive.metastore.client.socket.timeout 1 hour(s) hive_metastore_timeout false
Impala Daemon HDFS Advanced Configuration Snippet (Safety Valve) For advanced use only, a string to be inserted into hdfs-site.xml for this role only. impala_hdfs_site_conf_safety_valve false
Impala Daemon Hive Advanced Configuration Snippet (Safety Valve) For advanced use only, a string to be inserted into hive-site.xml for this role only. impala_hive_conf_safety_valve false
Impala Daemon Llama Site Advanced Configuration An XML snippet to append to llama-site.xml for Impala Daemons. This configuration only has effect on Impala versions 1.3 or greater. impala_llama_site_conf_safety_valve false
Impala Daemon Command Line Argument Advanced Configuration Snippet (Safety Valve) For advanced use only, key-value pairs (one on each line) to be added (verbatim) to Impala Daemon command-line flags. Key names should begin with a hyphen(-). For example: -log_filename=foo.log impalad_cmd_args_safety_valve false
Impala Daemon Fair Scheduler Advanced Configuration An XML string to use verbatim for the contents of fair-scheduler.xml for Impala Daemons. This configuration only has effect on Impala versions 1.3 or greater. impalad_fair_scheduler_safety_valve false
Impala Daemon HBase Advanced Configuration Snippet (Safety Valve) For advanced use only, a string to be inserted into hbase-site.xml for this role only. impalad_hbase_conf_safety_valve false
Result Cache Maximum Size Maximum number of query results a client may request to be cached on a per-query basis to support restarting fetches. This option guards against unreasonably large result caches requested by clients. Requests exceeding this maximum will be rejected. max_result_cache_size 100000 impalad_result_cache_max_size false
Impala Daemon Logging Advanced Configuration Snippet (Safety Valve) For advanced use only, a string to be inserted into log4j.properties for this role only. log4j_safety_valve false
Automatically Restart Process When set, this role's process is automatically (and transparently) restarted in the event of an unexpected failure. true process_auto_restart true

Logs

Display Name Description Related Name Default Value API Name Required
Impala Daemon Audit Log Directory The directory in which Impala Daemon audit event log files are written. If "Impala Audit Event Generation" property is enabled, Impala will generate its audit logs in this directory. audit_event_log_dir /var/log/impalad/audit audit_event_log_dir true
Enable Impala Audit Event Generation Enables audit event generation by Impala daemons. The audit log file will be placed in the directory specified by 'Impala Daemon Audit Log Directory' parameter. enable_audit_event_log false enable_audit_event_log false
Impala Daemon Log Directory Directory where Impala Daemon will place its log files. log_dir /var/log/impalad log_dir false
Impala Daemon Logging Threshold The minimum log level for Impala Daemon logs INFO log_threshold false
Impala Daemon Verbose Log Level Verbose logging level for the GLog logger. These messages are always logged at 'INFO' log level, so this setting has no effect if Logging Threshold is set to 'WARN' or above. GLOG_v 1 log_verbose_level false
Impala Daemon Log Buffer Level Buffer log messages logged at this level or lower (-1 means don't buffer; 0 means buffer INFO only; 1 means buffer WARNING only, ...) logbuflevel 0 logbuflevel false
Impala Daemon Maximum Audit Log File Size The maximum size (in queries) of the Impala Daemon audit event log file before a new one is created. max_audit_event_log_file_size 5000 line(s) max_audit_event_log_file_size false
Impala Daemon Max Log Size The maximum size, in megabytes, per log file for Impala Daemon 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
Query Monitoring Timeout The timeout used by the Cloudera Manager Agent's query monitor when communicating with the Impala Daemon web server, specified in seconds. 5.0 second(s) executing_queries_timeout_seconds false
Impala Daemon Connectivity Health Test Enables the health test that verifies the Impala Daemon is connected to the StateStore true impalad_connectivity_health_enabled false
Impala Daemon Connectivity Tolerance at Startup The amount of time to wait for the Impala Daemon to fully start up and connect to the StateStore before enforcing the connectivity check. 3 minute(s) impalad_connectivity_tolerance false
File Descriptor Monitoring Thresholds The health test thresholds of the number of file descriptors used. Specified as a percentage of file descriptor limit. Warning: 50.0 %, Critical: 70.0 % impalad_fd_thresholds false
Impala Daemon Host Health Test When computing the overall Impala Daemon health, consider the host's health. true impalad_host_health_enabled false
Impala Daemon Ready Status Health Check Enables the health check that determines if the Impala Daemon is ready to process queries. true impalad_ready_status_check_enabled false
Impala Daemon Ready Status Startup Tolerance The amount of time at Impala Daemon startup allowed for the Impala Daemon to start accepting new queries for processing. 3 minute(s) impalad_ready_status_check_startup_tolerance false
Impala Daemon Process Health Test Enables the health test that the Impala Daemon's process state is consistent with the role configuration true impalad_scm_health_enabled false
Impala Scratch Directories Free Space Monitoring Absolute Thresholds The health test thresholds for monitoring of free space on the filesystems that contain Impala's scratch directories. Warning: 10 GiB, Critical: 5 GiB impalad_scratch_directories_free_space_absolute_thresholds false
Impala Scratch Directories Free Space Monitoring Percentage Thresholds Configures the health check thresholds for monitoring free space on the filesystems that contain Impala's scratch directories. Specified as a percentage of the capacity on the filesystem. This setting is not used if a Scratch Directories Free Space Monitoring Absolute Thresholds setting is configured. Warning: Never, Critical: Never impalad_scratch_directories_free_space_percentage_thresholds false
Web Metric Collection Enables the health test that the Cloudera Manager Agent can successfully contact and gather metrics from the web server. true impalad_web_metric_collection_enabled false
Web Metric Collection Duration The health test thresholds on the duration of the metrics request to the web server. Warning: 10 second(s), Critical: Never impalad_web_metric_collection_thresholds 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
Resident Set Size Thresholds The health test thresholds on the resident size of the process. Warning: Never, Critical: Never process_resident_set_size_thresholds false
Query Monitoring Period The polling period of the Impala query monitor in the Cloudera Manager Agent, specified in seconds. If set to zero, query monitoring is disabled. 1.0 second(s) query_monitoring_period_seconds 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.
  • triggerExpression (mandatory) - a tsquery expression representing the trigger.
  • 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
Unexpected Exits Thresholds The health test thresholds for unexpected exits encountered within a recent period specified by the unexpected_exits_window configuration for the role. Warning: Never, Critical: Any unexpected_exits_thresholds false
Unexpected Exits Monitoring Period The period to review when computing unexpected exits. 5 minute(s) unexpected_exits_window false

Other

Display Name Description Related Name Default Value API Name Required
Impala Daemon Query Options Advanced Configuration Snippet (Safety Valve) A list of key-value pairs of additional query options to pass to the Impala Daemon command line, separated by ','. default_query_options default_query_options false
Impala Daemons Load Balancer Address of the load balancer used for Impala Daemons. Should be specified in host:port format. impalad_load_balancer false
Local UDF Library Dir User-defined function (UDF) libraries are copied from HDFS into this local directory. local_library_dir /var/lib/impala/udfs local_library_dir false
Impala Daemon Scratch Directories Directories where Impala Daemon will write data such as spilling information to disk to free up memory. This can potentially be large amounts of data. scratch_dirs scratch_dirs false

Performance

Display Name Description Related Name Default Value API Name Required
Maximum Process File Descriptors If configured, overrides the process soft and hard rlimits (also called ulimits) for file descriptors to the configured value. rlimit_fds false

Ports and Addresses

Display Name Description Related Name Default Value API Name Required
Impala Daemon Backend Port Port on which ImpalaBackendService is exported. be_port 22000 be_port false
Impala Daemon Beeswax Port Port on which Beeswax client requests are served by Impala Daemons. beeswax_port 21000 beeswax_port false
Impala Daemon HiveServer2 Port Port on which HiveServer2 client requests are served by Impala Daemons. hs2_port 21050 hs2_port false
Enable Impala Daemon Web Server Enable or disable the Impala Daemon web server. This web server contains useful information about Impala Daemon. enable_webserver true impalad_enable_webserver false
Impala Daemon HTTP Server Port Port where Impala debug web server runs. webserver_port 25000 impalad_webserver_port false
Llama Callback Port Port where Llama notification callback should be started llama_callback_port 28000 llama_callback_port false
StateStoreSubscriber Service Port Port where StateStoreSubscriberService is running. state_store_subscriber_port 23000 state_store_subscriber_port false

Resource Management

Display Name Description Related Name Default Value API Name Required
Impala Daemon Memory Limit Memory limit in bytes for Impala Daemon, enforced by the daemon itself. If reached, queries running on the Impala Daemon may be killed. Leave it blank to let Impala pick its own limit. Use a value of -1 B to specify no limit. mem_limit impalad_memory_limit false
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. memory.soft_limit_in_bytes -1 MiB rm_memory_soft_limit true

Security

Display Name Description Related Name Default Value API Name Required
SSL Certificate File Location The location of the debug webserver's SSL certificate file, in .pem format. If empty, webserver SSL support is not enabled. webserver_certificate_file webserver_certificate_file false
Impala Daemon Web Server User Password Password for Impala Daemon webserver authentication. webserver_htpassword_password webserver_htpassword_password false
Impala Daemon Web Server Username Username for Impala Daemon webserver authentication. webserver_htpassword_user webserver_htpassword_user false

impalallamaapplicationmasterdefaultgroup

Advanced

Display Name Description Related Name Default Value API Name Required
Enable Resource Caching Whether Llama should cache allocated resources on release. llama.am.cache.enabled true llama_am_cache_enabled false
Resource Caching Idle Timeout Timeout policy for resources being cached. llama.am.cache.eviction.timeout.policy.idle.timeout.ms 30 second(s) llama_am_cache_eviction_timeout_policy_idle_timeout_ms false
Anti-Deadlock Backoff Percentage Percentage of resources that will be backed off by the Impala ApplicationMaster anti-deadlock logic. Random reservations will be backed off until the percentage of backed off resources reaches this percentage. llama.am.gang.anti.deadlock.backoff.percent 30 % llama_am_gang_anti_deadlock_backoff_percent false
Anti-Deadlock Maximum Delay Maximum amount of time the backed off reservations will be in 'backed off' state. The actual amount time is a random value between the minimum and the maximum. llama.am.gang.anti.deadlock.max_delay_ms 30 second(s) llama_am_gang_anti_deadlock_max_delay_ms false
Anti-Deadlock Minimum Delay Minimum amount of time the backed off reservations will be in 'backed off' state. The actual amount time is a random value between the minimum and the maximum. llama.am.gang.anti.deadlock.min_delay_ms 10 second(s) llama_am_gang_anti_deadlock_min_delay_ms false
Anti-Deadlock No Allocation Limit Interval Interval of time without any new allocation that will trigger the Impala ApplicationMaster anti-deadlock logic. llama.am.gang.anti.deadlock.no.allocation.limit.ms 30 second(s) llama_am_gang_anti_deadlock_no_allocation_limit_ms false
Enable Resource Cache Normalization Whether to break resource requests into smaller requests of standard size before the resource cache. The sizes are taken from Yarn settings Container Memory Increment and Container Virtual CPU Cores Increment. llama.am.resource.normalizing.enabled true llama_am_resource_normalizing_enabled false
Maximum Client Notification Retries Maximum number of retries for a client notification. After the maximum number of client notification retries has been reached without success the client is considered lost and all its reservations are released. A successful client notification resets the retries count. llama.am.server.thrift.client.notifier.max.retries 5 llama_am_server_thrift_client_notifier_max_retries false
Client Notification Retry Interval Client notification retry interval, in milliseconds. llama.am.server.thrift.client.notifier.retry.interval.ms 5 second(s) llama_am_server_thrift_client_notifier_retry_interval_ms false
Impala Llama ApplicationMaster Advanced Configuration Snippet (Safety Valve) for llama-site.xml For advanced use only, a string to be inserted into llama-site.xml for this role only. llama_config_valve false
Fair Scheduler XML Advanced Configuration Snippet (Safety Valve) Enter an XML string that will be inserted verbatim into the Fair Scheduler allocations file. Overrides the configuration set using the Pools configuration UI. This configuration only has effect on Impala versions 1.3 or greater. llama_fair_scheduler_safety_valve false
Java Configuration Options for Llama 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. llama_java_opts false
Impala Llama ApplicationMaster Logging Advanced Configuration Snippet (Safety Valve) 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. true process_auto_restart true
Llama System Group The group that the Llama processes should run as. llama process_groupname true
Llama System User The user that the Llama process should run as. llama process_username true

Logs

Display Name Description Related Name Default Value API Name Required
Llama Log Directory Directory where Llama will place its log files. llama_log_dir /var/log/impala-llama llama_log_dir false
Impala Llama ApplicationMaster Logging Threshold The minimum log level for Impala Llama ApplicationMaster logs INFO log_threshold false
Impala Llama ApplicationMaster Maximum Log File Backups The maximum number of rolled log files to keep for Impala Llama ApplicationMaster logs. Typically used by log4j. 10 max_log_backup_index false
Impala Llama ApplicationMaster Max Log Size The maximum size, in megabytes, per log file for Impala Llama ApplicationMaster 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
File Descriptor Monitoring Thresholds The health test thresholds of the number of file descriptors used. Specified as a percentage of file descriptor limit. Warning: 50.0 %, Critical: 70.0 % llama_fd_thresholds false
Impala Llama ApplicationMaster Host Health Test When computing the overall Impala Llama ApplicationMaster health, consider the host's health. true llama_host_health_enabled false
Impala Llama ApplicationMaster Process Health Test Enables the health test that the Impala Llama ApplicationMaster's process state is consistent with the role configuration true llama_scm_health_enabled 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.
  • triggerExpression (mandatory) - a tsquery expression representing the trigger.
  • 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
Unexpected Exits Thresholds The health test thresholds for unexpected exits encountered within a recent period specified by the unexpected_exits_window configuration for the role. Warning: Never, Critical: Any unexpected_exits_thresholds false
Unexpected Exits Monitoring Period The period to review when computing unexpected exits. 5 minute(s) unexpected_exits_window false

Other

Display Name Description Related Name Default Value API Name Required
Core Queues Queues Llama ApplicationMaster should connect to at start up. llama.am.core.queues llama_am_core_queues false
Administrative Interface ACLs ACL for Impala ApplicationMaster admins. The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed. These take effect only if security is enabled. llama.am.server.thrift.admin.acl * llama_am_server_thrift_admin_acl false
Client ACLs ACL for Impala ApplicationMaster clients. The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed. These take effect only if security is enabled. llama.am.server.thrift.client.acl * llama_am_server_thrift_client_acl false

Performance

Display Name Description Related Name Default Value API Name Required
Queue Expiration Age Time in milliseconds after which Llama will discard its AM for a queue that has been empty of reservations. Does not apply to queues specified with the Core Queues property. llama.am.queue.expire.ms 5 minute(s) llama_am_queue_expire_ms false
AM Heartbeat Interval Llama ApplicationMaster heartbeat interval, in milliseconds. On each heartbeat the ApplicationMaster submits new reservations to YARN ResourceManager and gets updates from it. llama.am.server.thrift.client.notifier.heartbeat.ms 5 second(s) llama_am_server_thrift_client_notifier_heartbeat_ms false
Thrift Server Maximum Threads Maximum number of threads used by the Llama ApplicationMaster auxiliary service uses for serving client requests. llama.am.server.thrift.server.max.threads 50 llama_am_server_thrift_server_max_threads false
Thrift Server Minimum Threads Minimum number of threads used by the Llama ApplicationMaster auxiliary service uses for serving client requests. llama.am.server.thrift.server.min.threads 10 llama_am_server_thrift_server_min_threads false
Thrift Transport Timeout Socket time, in milliseconds, used Llama ApplicationMaster auxiliary service for all its server and client Thrift connections. llama.am.server.thrift.transport.timeout.ms 1 minute(s) llama_am_server_thrift_transport_timeout_ms false
Maximum Process File Descriptors If configured, overrides the process soft and hard rlimits (also called ulimits) for file descriptors to the configured value. rlimit_fds false

Ports and Addresses

Display Name Description Related Name Default Value API Name Required
Llama Thrift Admin Port Port on which the Llama ApplicationMaster listens to administrative requests on its administrative Thrift interface. llama.am.server.thrift.admin.address 15002 llama_am_server_thrift_admin_address false
Bind Impala Llama ApplicationMaster to Wildcard Address If enabled, the Impala Llama ApplicationMaster binds to the wildcard address ("0.0.0.0") on all of its ports. false llama_bind_wildcard false
Llama HTTP Port Port on which the Llama ApplicationMaster listens to HTTP requests. llama.am.server.thrift.http.address 15001 llama_http_port false
Llama Thrift Port Port on which the Llama ApplicationMaster serves its Thrift interface. llama.am.server.thrift.address 15000 llama_port false

Resource Management

Display Name Description Related Name Default Value API Name Required
Java Heap Size of Impala Llama ApplicationMaster in Bytes Maximum size in bytes for the Java Process heap memory. Passed to Java -Xmx. 256 MiB llama_java_heapsize false
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. memory.soft_limit_in_bytes -1 MiB rm_memory_soft_limit true

Stacks Collection

Display Name Description Related Name Default Value API Name Required
Stacks Collection Data Retention 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. stacks_collection_method jstack stacks_collection_method false

impalastatestoredefaultgroup

Advanced

Display Name Description Related Name Default Value API Name Required
Automatically Restart Process When set, this role's process is automatically (and transparently) restarted in the event of an unexpected failure. true process_auto_restart true
Statestore Command Line Argument Advanced Configuration Snippet (Safety Valve) For advanced use only, key-value pairs (one on each line) to be added (verbatim) to StateStore command line flags. statestore_cmd_args_safety_valve false

Logs

Display Name Description Related Name Default Value API Name Required
StateStore Log Directory Directory where StateStore will place its log files. log_dir /var/log/statestore log_dir false
Impala StateStore Logging Threshold The minimum log level for Impala StateStore logs INFO log_threshold false
StateStore Verbose Log Level Verbose logging level for the GLog logger. These messages are always logged at 'INFO' log level, so this setting has no effect if Logging Threshold is set to 'WARN' or above. GLOG_v 1 log_verbose_level false
StateStore Log Buffer Level Buffer log messages logged at this level or lower (-1 means don't buffer; 0 means buffer INFO only; 1 means buffer WARNING only, ...) logbuflevel 0 logbuflevel false
Impala StateStore Max Log Size The maximum size, in megabytes, per log file for Impala StateStore 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
Resident Set Size Thresholds The health test thresholds on the resident size of the process. Warning: Never, Critical: Never process_resident_set_size_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.
  • triggerExpression (mandatory) - a tsquery expression representing the trigger.
  • 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. Warning: 50.0 %, Critical: 70.0 % statestore_fd_thresholds false
Impala StateStore Host Health Test When computing the overall Impala StateStore health, consider the host's health. true statestore_host_health_enabled false
Impala StateStore Process Health Test Enables the health test that the Impala StateStore's process state is consistent with the role configuration true statestore_scm_health_enabled false
Health Check Startup Tolerance The amount of time allowed after this role is started that failures of health checks that rely on communication with this role will be tolerated. 5 minute(s) statestore_startup_tolerance false
Web Metric Collection Enables the health test that the Cloudera Manager Agent can successfully contact and gather metrics from the web server. true statestore_web_metric_collection_enabled false
Web Metric Collection Duration The health test thresholds on the duration of the metrics request to the web server. Warning: 10 second(s), Critical: Never statestore_web_metric_collection_thresholds false
Unexpected Exits Thresholds The health test thresholds for unexpected exits encountered within a recent period specified by the unexpected_exits_window configuration for the role. Warning: Never, Critical: Any unexpected_exits_thresholds false
Unexpected Exits Monitoring Period The period to review when computing unexpected exits. 5 minute(s) unexpected_exits_window false

Other

Display Name Description Related Name Default Value API Name Required
Enable StateStore Web Server Enable/Disable StateStore web server. This web server contains useful information about StateStore daemon. enable_webserver true statestore_enable_webserver false

Performance

Display Name Description Related Name Default Value API Name Required
Maximum Process File Descriptors If configured, overrides the process soft and hard rlimits (also called ulimits) for file descriptors to the configured value. rlimit_fds false
StateStore Worker Threads Number of worker threads for the thread manager underlying the State Store Thrift server. state_store_num_server_worker_threads 4 state_store_num_server_worker_threads false
Maximum StateStore Pending Tasks Maximum number of tasks allowed to be pending at the thread manager underlying the State Store Thrift server (0 allows infinitely many pending tasks) state_store_pending_task_count_max 0 state_store_pending_task_count_max false

Ports and Addresses

Display Name Description Related Name Default Value API Name Required
StateStore Service Port Port where StateStoreService is exported. state_store_port 24000 state_store_port false
StateStore HTTP Server Port Port where StateStore debug web server runs. webserver_port 25010 statestore_webserver_port false

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. memory.soft_limit_in_bytes -1 MiB rm_memory_soft_limit true

Security

Display Name Description Related Name Default Value API Name Required
SSL Certificate File Location The location of the debug webserver's SSL certificate file, in .pem format. If empty, webserver SSL support is not enabled. webserver_certificate_file webserver_certificate_file false
Statestore Web Server User Password Password for Statestore webserver authentication. webserver_htpassword_password webserver_htpassword_password false
Statestore Web Server Username Username for Statestore webserver authentication. webserver_htpassword_user webserver_htpassword_user false

service_wide

Advanced

Display Name Description Related Name Default Value API Name Required
Enable Core Dump Used to generate a core dump to get more information about an Impala crash. Unless otherwise configured system wide using /proc/sys/kernel/core_pattern, the dump is generated in the 'current directory' of the Impala process (usually a subdirectory of the /var/run/cloudera-scm-agent/process directory). The core file can be very large. false enable_core_dump false
Maximum HBase Client Retries Maximum number of HBase client retries for Impala. Used as a maximum for all operations such as fetching of the root region from the root RegionServer, getting a cell's value, and starting a row update. Overrides configuration in the HBase service. hbase.client.retries.number 3 hbase_client_retries_number false
HBase RPC Timeout Timeout in milliseconds for all HBase RPCs made by Impala. Overrides configuration in HBase service. hbase.rpc.timeout 3 second(s) hbase_rpc_timeout false
Impala Command Line Argument Advanced Configuration Snippet (Safety Valve) For advanced use only, key-value pairs (one on each line) to be added (verbatim) to Impala Daemon command-line flags. Applies to all roles in this service. Key names should begin with a hyphen(-). For example: -log_filename=foo.log impala_cmd_args_safety_valve false
Fair Scheduler Configuration Rules A list specifying the rules to run to determine which Fair Scheduler configuration to use. Typically edited using the Rules configuration UI. This configuration only has effect on Impala versions 1.3 or greater. [] impala_schedule_rules false
Fair Scheduler Allocations JSON representation of all the configurations that the Fair Scheduler can take on across all schedules. Typically edited using the Pools configuration UI. This configuration only has effect on Impala versions 1.3 or greater. defaultMinSharePreemptionTimeout:null, defaultQueueSchedulingPolicy:null, fairSharePreemptionTimeout:null, queueMaxAppsDefault:null, queuePlacementRules:null, queues:[aclAdministerApps:null, aclSubmitApps:null, minSharePreemptionTimeout:null, name:root, queues:[aclAdministerApps:null, aclSubmitApps:null, minSharePreemptionTimeout:null, name:default, queues:[], schedulablePropertiesList:[impalaMaxMemory:null, impalaMaxQueuedQueries:null, impalaMaxRunningQueries:null, maxResources:null, maxRunningApps:null, minResources:null, scheduleName:default, weight:null], schedulingPolicy:null], schedulablePropertiesList:[impalaMaxMemory:null, impalaMaxQueuedQueries:null, impalaMaxRunningQueries:null, maxResources:null, maxRunningApps:null, minResources:null, scheduleName:default, weight:null], schedulingPolicy:null], userMaxAppsDefault:null, users:[] impala_scheduled_allocations false
Impala Service Environment Advanced Configuration Snippet (Safety Valve) 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. impala_service_env_safety_valve false
Impala Service Advanced Configuration Snippet (Safety Valve) for sentry-site.xml For advanced use only, a string to be inserted into sentry-site.xml. Applies to configurations of all roles in this service except client configuration. impalad_sentry_safety_valve false
Impala Client Advanced Configuration Snippet (Safety Valve) for navigator.client.properties For advanced use only, a string to be inserted into the client configuration for navigator.client.properties. navigator_client_config_safety_valve false
Impala System Group (except Llama) The group that this Impala's processes should run as (except Llama, which has its own group). impala process_groupname true
Impala System User (except Llama) The user that this Impala's processes should run as (except Llama, which has its own user). impala process_username true
Use Debug Build Use debug build of Impala binaries when starting roles. Useful when performing diagnostic activities to get more information in the stacktrace or core dump. false use_debug_build false

Cloudera Navigator

Display Name Description Related Name Default Value API Name Required
Enable Collection Enable collection of audit events from the service's roles. true navigator_audit_enabled false
Event Filter Event filters are defined in a JSON object like the following: { "defaultAction" : ("accept", "discard"), "rules" : [ { "action" : ("accept", "discard"), "fields" : [ { "name" : "fieldName", "match" : "regex" } ] } ] } A filter has a default action and a list of rules, in order of precedence. Each rule defines an action, and a list of fields to match against the audit event. A rule is "accepted" if all the listed field entries match the audit event. At that point, the action declared by the rule is taken. If no rules match the event, the default action is taken. Actions default to "accept" if not defined in the JSON object. The following is the list of fields that can be filtered for Impala events:
  • userName: the user performing the action.
  • ipAddress: the IP from where the request originated.
  • operation: the Impala operation being performed.
  • databaseName: the databaseName for the operation.
  • tableName: the tableName for the operation.
 navigator.event.filter navigator_audit_event_filter false
Queue Policy Action to take when the audit event queue is full. Drop the event or shutdown the affected process. navigator.batch.queue_policy DROP navigator_audit_queue_policy false
Event Tracker Configures the rules for event tracking and coalescing. This feature is used to define equivalency between different audit events. When events match, according to a set of configurable parameters, only one entry in the audit list is generated for all the matching events. Tracking works by keeping a reference to events when they first appear, and comparing other incoming events against the "tracked" events according to the rules defined here. Event trackers are defined in a JSON object like the following: { "timeToLive" : [integer], "fields" : [ { "type" : [string], "name" : [string] } ] } Where:
  • timeToLive: maximum amount of time an event will be tracked, in milliseconds. Must be provided. This defines how long, since it's first seen, an event will be tracked. A value of 0 disables tracking.
  • fields: list of fields to compare when matching events against tracked events.
Each field has an evaluator type associated with it. The evaluator defines how the field data is to be compared. The following evaluators are available:
  • value: uses the field value for comparison.
  • userName: treats the field value as a userName, and ignores any host-specific data. This is useful for environment using Kerberos, so that only the principal name and realm are compared.
The following is the list of fields that can be used to compare Impala events:
  • username: the user performing the action.
  • ipAddress: the IP from where the request originated.
  • operation: the Impala operation being performed.
  • databaseName: the database affected by the operation.
  • tableName: the table affected by the operation.
 navigator_event_tracker navigator_event_tracker false

Monitoring

Display Name Description Related Name Default Value API Name Required
Admin Users Query List Visibility Settings Controls which queries admin users can see in the queries list view ALL admin_query_list_settings true
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
Assignment Locality Minimum Assignments The minimum number of assignments that must occur during the test time period before the threshold values will be checked. Until this number of assignments have been observed in the test time period the health test will be disabled. 10 impala_assignment_locality_minimum false
Assignment Locality Ratio Thresholds The health test thresholds for assignment locality. Specified as a percentage of total assignments. Warning: 80.0 %, Critical: 5.0 % impala_assignment_locality_thresholds false
Assignment Locality Monitoring Period The time period over which to compute the assignment locality ratio. Specified in minutes. 15 minute(s) impala_assignment_locality_window false
Impala Catalog Server Role Health Test When computing the overall IMPALA health, consider Impala Catalog Server's health true impala_catalogserver_health_enabled false
Healthy Impala Daemon Monitoring Thresholds The health test thresholds of the overall Impala Daemon health. The check returns "Concerning" health if the percentage of "Healthy" Impala Daemons falls below the warning threshold. The check is unhealthy if the total percentage of "Healthy" and "Concerning" Impala Daemons falls below the critical threshold. Warning: 95.0 %, Critical: 90.0 % impala_impalads_healthy_thresholds false
Healthy Impala Llama ApplicationMaster Monitoring Thresholds The health test thresholds of the overall Impala Llama ApplicationMaster health. The check returns "Concerning" health if the percentage of "Healthy" Impala Llama ApplicationMasters falls below the warning threshold. The check is unhealthy if the total percentage of "Healthy" and "Concerning" Impala Llama ApplicationMasters falls below the critical threshold. Warning: 99.0 %, Critical: 51.0 % impala_llamas_healthy_thresholds false
Impala Query Aggregates Controls the aggregate metrics generated for Impala queries. The structure is a JSON list of the attributes to aggregate and the entities to aggregate to. For example, if the attributeName is 'hdfs_bytes_read' and the aggregationTargets is ['USER'] then the Service Monitor will create the metric 'impala_query_hdfs_bytes_read_rate' and, every ten minutes, will record the total hdfs bytes read for each user across all their Impala queries. By default it will also record the number of queries issues ('num_impala_queries_rate') for both users and pool. For a full list of the supported attributes see the Impala search page. Note that the valid aggregation targets are USER, YARN_POOL, and IMPALA (the service), and that these aggregate metrics can be viewed on both the reports and charts search pages. [ attributeName: hdfs_bytes_read, aggregationTargets: [USER, YARN_POOL, IMPALA] , attributeName: hdfs_bytes_written, aggregationTargets: [USER, YARN_POOL, IMPALA] , attributeName: thread_cpu_time, aggregationTargets: [USER, YARN_POOL, IMPALA] , attributeName: bytes_streamed, aggregationTargets: [USER, YARN_POOL, IMPALA] , attributeName: cm_cpu_milliseconds, aggregationTargets: [USER] ] impala_query_aggregates false
Impala StateStore Role Health Test When computing the overall IMPALA health, consider Impala StateStore's health true impala_statestore_health_enabled 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.
  • triggerExpression (mandatory) - a tsquery expression representing the trigger.
  • 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.		 [] service_triggers true
Service Monitor Derived Configs Advanced Configuration Snippet (Safety Valve) For advanced use only, a list of derived configuration properties that will be used by the Service Monitor instead of the default ones. smon_derived_configs_safety_valve false
Non-Admin Users Query List Visibility Settings Controls which queries a non-admin user can see in the queries list view ALL user_query_list_settings true

Other

Display Name Description Related Name Default Value API Name Required
Enable Dynamic Resource Pools Use Dynamic Resource Pools to configure resource pools used for admission control and resource management for this Impala service. These features are only supported in Impala 1.3 or later deployments. true admission_control_enabled false
HBase Service Name of the HBase service that this Impala service instance depends on hbase_service false
HDFS Service Name of the HDFS service that this Impala service instance depends on hdfs_service true
Hive Service Name of the Hive service that this Impala service instance depends on hive_service true
YARN Service for Resource Management Name of YARN service to use for resource management integration between Impala and YARN. This service dependency and the existence of a Llama role is required for using said integration. yarn_service false

Performance

Display Name Description Related Name Default Value API Name Required
Enable HDFS Short Circuit Read Enable HDFS short circuit read. This allows a client co-located with the DataNode to read HDFS file blocks directly. This gives a performance boost to distributed clients that are aware of locality. dfs.client.read.shortcircuit true dfs_client_read_shortcircuit false
StateStoreSubscriber Timeout Time in seconds before Impala Daemon or Catalog Server times out with the StateStore. statestore_subscriber_timeout_seconds 30 second(s) statestore_subscriber_timeout false

Policy File-Based Sentry

Display Name Description Related Name Default Value API Name Required
Proxy User Configuration Specifies the set of authorized proxy users (users who can impersonate other users during authorization) and whom they are allowed to impersonate. Input is a semicolon-separated list of key=value pairs of authorized proxy users to the user(s) they can impersonate. These users are specified as a comma separated list of short usernames, or '*' to indicate all users. For example: joe=alice,bob;hue=*;admin=*. Only valid when Sentry is enabled. authorized_proxy_user_config hue=* impala_authorized_proxy_user_config false
Enable Sentry Authorization using Policy Files Use Sentry to enable role-based, fine-grained authorization. This configuration enables Sentry using policy files. To enable Sentry using Sentry service instead, add Sentry service as a dependency to Impala service. Sentry service provides concurrent and secure access to authorization policy metadata and is the recommended option for enabling Sentry. Sentry is supported only on Impala 1.1 or later deployments. impala.sentry.enabled false sentry_enabled false

Security

Display Name Description Related Name Default Value API Name Required
Enable SSL for Impala Client Services Enable support for encrypted client-server communication using Secure Socket Layer (SSL) for Impala client services. This is only applicable to non-Kerberos environments. client_services_ssl_enabled false client_services_ssl_enabled false
Enable LDAP Authentication If true, LDAP-based authentication for users is enabled. enable_ldap_auth false enable_ldap_auth false
LDAP URI The URI of the LDAP server to use if LDAP is enabled. Typically, the URI should be prefixed with ldap:// or ldaps://. The URI can optionally specify the port, for example: ldap://ldap_server.example.com:389. ldaps is only supported in Impala 1.4 or CDH 5.1 or higher, and usually requires that you specify a port. ldap_uri ldap://ldap_server.example.com impala_ldap_uri false
Kerberos Re-init Interval Number of minutes between reestablishing our ticket with the Kerberos server. kerberos_reinit_interval 1 hour(s) kerberos_reinit_interval false
SSL Server Private Key Local path to the SSL private key file. ssl_private_key ssl_private_key false
SSL Server Certificate Local path to the SSL server certificate file. ssl_server_certificate ssl_server_certificate false