Amazon EMR release 6.2.0 - Amazon EMR
6.2.0 application versions6.2.0 release notes6.2.0 component versions6.2.0 configuration classifications

Amazon EMR release 6.2.0

6.2.0 application versions

The following applications are supported in this release: Flink, Ganglia, HBase, HCatalog, Hadoop, Hive, Hudi, Hue, JupyterEnterpriseGateway, JupyterHub, Livy, MXNet, Oozie, Phoenix, Pig, Presto, PrestoSQL, Spark, Sqoop, TensorFlow, Tez, Zeppelin, and ZooKeeper.

The table below lists the application versions available in this release of Amazon EMR and the application versions in the preceding three Amazon EMR releases (when applicable).

For a comprehensive history of application versions for each release of Amazon EMR, see the following topics:

Application version information
emr-6.2.0 emr-6.1.1 emr-6.1.0 emr-6.0.1
AWS SDK for Java 1.11.8801.11.8281.11.8281.11.711
Python 2.7, 3.72.7, 3.72.7, 3.72.7, 3.7
Scala 2.12.102.12.102.12.102.12.10
AmazonCloudWatchAgent - - - -
Delta - - - -
Flink1.11.21.11.01.11.0 -
Ganglia3.7.23.7.23.7.23.7.2
HBase2.2.6-amzn-02.2.52.2.52.2.3
HCatalog3.1.23.1.23.1.23.1.2
Hadoop3.2.13.2.13.2.13.2.1
Hive3.1.23.1.23.1.23.1.2
Hudi0.6.0-amzn-10.5.2-incubating-amzn-20.5.2-incubating-amzn-20.5.0-incubating-amzn-1
Hue4.8.04.7.14.7.14.4.0
Iceberg - - - -
JupyterEnterpriseGateway2.1.0 - - -
JupyterHub1.1.01.1.01.1.01.0.0
Livy0.7.00.7.00.7.00.6.0
MXNet1.7.01.6.01.6.01.5.1
Mahout - - - -
Oozie5.2.05.2.05.2.05.1.0
Phoenix5.0.05.0.05.0.05.0.0
Pig0.17.00.17.00.17.0 -
Presto0.238.30.2320.2320.230
Spark3.0.13.0.03.0.02.4.4
Sqoop1.4.71.4.71.4.7 -
TensorFlow2.3.12.1.02.1.01.14.0
Tez0.9.20.9.20.9.20.9.2
Trino (PrestoSQL)343338338 -
Zeppelin0.9.00.9.00.9.00.9.0
ZooKeeper3.4.143.4.143.4.143.4.14

6.2.0 release notes

The following release notes include information for Amazon EMR release 6.2.0. Changes are relative to 6.1.0.

Initial release date: Dec 09, 2020

Last updated date: Oct 04, 2021

Supported applications

  • AWS SDK for Java version 1.11.828

  • emr-record-server version 1.7.0

  • Flink version 1.11.2

  • Ganglia version 3.7.2

  • Hadoop version 3.2.1-amzn-1

  • HBase version 2.2.6-amzn-0

  • HBase-operator-tools 1.0.0

  • HCatalog version 3.1.2-amzn-0

  • Hive version 3.1.2-amzn-3

  • Hudi version 0.6.0-amzn-1

  • Hue version 4.8.0

  • JupyterHub version 1.1.0

  • Livy version 0.7.0

  • MXNet version 1.7.0

  • Oozie version 5.2.0

  • Phoenix version 5.0.0

  • Pig version 0.17.0

  • Presto version 0.238.3-amzn-1

  • PrestoSQL version 343

  • Spark version 3.0.1-amzn-0

  • spark-rapids 0.2.0

  • TensorFlow version 2.3.1

  • Zeppelin version 0.9.0-preview1

  • Zookeeper version 3.4.14

  • Connectors and drivers: DynamoDB Connector 4.16.0

New features

  • HBase: Removed rename in commit phase and added persistent HFile tracking. See Persistent HFile Tracking in the Amazon EMR Release Guide.

  • HBase: Backported Create a config that forces to cache blocks on compaction.

  • PrestoDB: Improvements to Dynamic Partition Pruning. Rule-based Join Reorder works on non-partitioned data.

  • Scoped managed policies: To align with AWS best practices, Amazon EMR has introduced v2 EMR-scoped default managed policies as replacements for policies that will be deprecated. See Amazon EMR Managed Policies.

  • Instance Metadata Service (IMDS) V2 support status: For Amazon EMR 6.2 or later, Amazon EMR components use IMDSv2 for all IMDS calls. For IMDS calls in your application code, you can use both IMDSv1 and IMDSv2, or configure the IMDS to use only IMDSv2 for added security. If you disable IMDSv1 in earlier Amazon EMR 6.x releases, it causes cluster startup failure.

Changes, enhancements, and resolved issues

  • This is a release to fix issues with Amazon EMR Scaling when it fails to scale up/scale down a cluster successfully or causes application failures.

  • Fixed an issue where scaling requests failed for a large, highly utilized cluster when Amazon EMR on-cluster daemons were running health checking activities, such as gathering YARN node state and HDFS node state. This was happening because on-cluster daemons were not able to communicate the health status data of a node to internal Amazon EMR components.

  • Improved EMR on-cluster daemons to correctly track the node states when IP addresses are reused to improve reliability during scaling operations.

  • SPARK-29683. Fixed an issue where job failures occurred during cluster scale-down as Spark was assuming all available nodes were deny-listed.

  • YARN-9011. Fixed an issue where job failures occurred due to a race condition in YARN decommissioning when cluster tried to scale up or down.

  • Fixed issue with step or job failures during cluster scaling by ensuring that the node states are always consistent between the Amazon EMR on-cluster daemons and YARN/HDFS.

  • Fixed an issue where cluster operations such as scale down and step submission failed for Amazon EMR clusters enabled with Kerberos authentication. This was because the Amazon EMR on-cluster daemon did not renew the Kerberos ticket, which is required to securely communicate with HDFS/YARN running on the primary node.

  • Newer Amazon EMR releases fix the issue with a lower "Max open files" limit on older AL2 in Amazon EMR. Amazon EMR releases 5.30.1, 5.30.2, 5.31.1, 5.32.1, 6.0.1, 6.1.1, 6.2.1, 5.33.0, 6.3.0 and later now include a permanent fix with a higher "Max open files" setting.

  • Spark: Performance improvements in Spark runtime.

Known issues

  • Amazon EMR 6.2 has incorrect permissions set on the /etc/cron.d/libinstance-controller-java file in EMR 6.2.0. Permissions on the file are 645 (-rw-r--r-x), when they should be 644 (-rw-r--r--). As a result, Amazon EMR version 6.2 does not log instance-state logs, and the /emr/instance-logs directory is empty. This issue is fixed in Amazon EMR 6.3.0 and later.

    To work around this issue, run the following script as a bootstrap action at cluster launch. 

    #!/bin/bash
sudo chmod 644 /etc/cron.d/libinstance-controller-java

  • For Amazon EMR 6.2.0 and 6.3.0 private subnet clusters, you cannot access the Ganglia web UI. You will get an "access denied (403)" error. Other web UIs, such as Spark, Hue, JupyterHub, Zeppelin, Livy, and Tez are working normally. Ganglia web UI access on public subnet clusters are also working normally. To resolve this issue, restart httpd service on the primary node with sudo systemctl restart httpd. This issue is fixed in Amazon EMR 6.4.0.

  • There is an issue in Amazon EMR 6.2.0 where httpd continuously fails, causing Ganglia to be unavailable. You get a "cannot connect to the server" error. To fix a cluster that is already running with this issue, SSH to the cluster primary node and add the line Listen 80 to the file httpd.conf located at /etc/httpd/conf/httpd.conf. This issue is fixed in Amazon EMR 6.3.0.

  • HTTPD fails on EMR 6.2.0 clusters when you use a security configuration. This makes the Ganglia web application user interface unavailable. To access the Ganglia web application user interface, add Listen 80 to the /etc/httpd/conf/httpd.conf file on the primary node of your cluster. For information about connecting to your cluster, see Connect to the Primary Node Using SSH.

    EMR Notebooks also fail to establish a connection with EMR 6.2.0 clusters when you use a security configuration. The notebook will fail to list kernels and submit Spark jobs. We recommend that you use EMR Notebooks with another version of Amazon EMR instead.

  • Lower "Max open files" limit on older AL2 [fixed in newer releases]. Amazon EMR releases: emr-5.30.x, emr-5.31.0, emr-5.32.0, emr-6.0.0, emr-6.1.0, and emr-6.2.0 are based on older versions ofAmazon Linux 2 (AL2), which have a lower ulimit setting for "Max open files" when Amazon EMR clusters are created with the default AMI. Amazon EMR releases 5.30.1, 5.30.2, 5.31.1, 5.32.1, 6.0.1, 6.1.1, 6.2.1, 5.33.0, 6.3.0 and later include a permanent fix with a higher "Max open files" setting. Releases with the lower open file limit causes a "Too many open files" error when submitting Spark job. In the impacted releases, the Amazon EMR default AMI has a default ulimit setting of 4096 for "Max open files," which is lower than the 65536 file limit in the latestAmazon Linux 2 AMI. The lower ulimit setting for "Max open files" causes Spark job failure when the Spark driver and executor try to open more than 4096 files. To fix the issue, Amazon EMR has a bootstrap action (BA) script that adjusts the ulimit setting at cluster creation.

    If you are using an older Amazon EMR version that doesn't have the permanent fix for this issue, the following workaround lets you to explicitly set the instance-controller ulimit to a maximum of 65536 files.

    Explicitly set a ulimit from the command line

    1. Edit /etc/systemd/system/instance-controller.service to add the following parameters to Service section.

      LimitNOFILE=65536

      LimitNPROC=65536

    2. Restart InstanceController

      $ sudo systemctl daemon-reload

      $ sudo systemctl restart instance-controller

    Set a ulimit using bootstrap action (BA)

    You can also use a bootstrap action (BA) script to configure the instance-controller ulimit to 65536 files at cluster creation.

    #!/bin/bash
for user in hadoop spark hive; do
sudo tee /etc/security/limits.d/$user.conf << EOF
$user - nofile 65536
$user - nproc 65536
EOF
done
for proc in instancecontroller logpusher; do
sudo mkdir -p /etc/systemd/system/$proc.service.d/
sudo tee /etc/systemd/system/$proc.service.d/override.conf << EOF
[Service]
LimitNOFILE=65536
LimitNPROC=65536
EOF
pid=$(pgrep -f aws157.$proc.Main)
sudo prlimit --pid $pid --nofile=65535:65535 --nproc=65535:65535
done
sudo systemctl daemon-reload
  • Important

    Amazon EMR 6.1.0 and 6.2.0 include a performance issue that can critically affect all Hudi insert, upsert, and delete operations. If you plan to use Hudi with Amazon EMR 6.1.0 or 6.2.0, you should contact AWS support to obtain a patched Hudi RPM.

  • Important

    EMR clusters that run Amazon Linux or Amazon Linux 2 Amazon Machine Images (AMIs) use default Amazon Linux behavior, and do not automatically download and install important and critical kernel updates that require a reboot. This is the same behavior as other Amazon EC2 instances that run the default Amazon Linux AMI. If new Amazon Linux software updates that require a reboot (such as kernel, NVIDIA, and CUDA updates) become available after an Amazon EMR release becomes available, EMR cluster instances that run the default AMI do not automatically download and install those updates. To get kernel updates, you can customize your Amazon EMR AMI to use the latest Amazon Linux AMI.

  • Amazon EMR 6.2.0 Maven artifacts are not published. They will be published with a future release of Amazon EMR.

  • Persistent HFile tracking using the HBase storefile system table does not support the HBase region replication feature. For more information about HBase region replication, see Timeline-consistent High Available Reads.

  • Amazon EMR 6.x and EMR 5.x Hive bucketing version differences

    EMR 5.x uses OOS Apache Hive 2, while in EMR 6.x uses OOS Apache Hive 3. The open source Hive2 uses Bucketing version 1, while open source Hive3 uses Bucketing version 2. This bucketing version difference between Hive 2 (EMR 5.x) and Hive 3 (EMR 6.x) means Hive bucketing hashing functions differently. See the example below.

    The following table is an example created in EMR 6.x and EMR 5.x, respectively.

    -- Using following LOCATION in EMR 6.x
CREATE TABLE test_bucketing (id INT, desc STRING)
PARTITIONED BY (day STRING)
CLUSTERED BY(id) INTO 128 BUCKETS
LOCATION 's3://your-own-s3-bucket/emr-6-bucketing/';

-- Using following LOCATION in EMR 5.x 
LOCATION 's3://your-own-s3-bucket/emr-5-bucketing/';

    Inserting the same data in both EMR 6.x and EMR 5.x.

    INSERT INTO test_bucketing PARTITION (day='01') VALUES(66, 'some_data');
INSERT INTO test_bucketing PARTITION (day='01') VALUES(200, 'some_data');

    Checking the S3 location, shows the bucketing file name is different, because the hashing function is different between EMR 6.x (Hive 3) and EMR 5.x (Hive 2).

    [hadoop@ip-10-0-0-122 ~]$ aws s3 ls s3://your-own-s3-bucket/emr-6-bucketing/day=01/
2020-10-21 20:35:16         13 000025_0
2020-10-21 20:35:22         14 000121_0
[hadoop@ip-10-0-0-122 ~]$ aws s3 ls s3://your-own-s3-bucket/emr-5-bucketing/day=01/
2020-10-21 20:32:07         13 000066_0
2020-10-21 20:32:51         14 000072_0

    You can also see the version difference by running the following command in Hive CLI in EMR 6.x. Note that it returns bucketing version 2.

    hive> DESCRIBE FORMATTED test_bucketing;
...
Table Parameters:
    bucketing_version       2
...

  • Known issue in clusters with multiple primary nodes and Kerberos authentication

    If you run clusters with multiple primary nodes and Kerberos authentication in Amazon EMR releases 5.20.0 and later, you may encounter problems with cluster operations such as scale down or step submission, after the cluster has been running for some time. The time period depends on the Kerberos ticket validity period that you defined. The scale-down problem impacts both automatic scale-down and explicit scale down requests that you submitted. Additional cluster operations can also be impacted.

    Workaround:

    • SSH as hadoop user to the lead primary node of the EMR cluster with multiple primary nodes.

    • Run the following command to renew Kerberos ticket for hadoop user. 

      kinit -kt <keytab_file> <principal>

      Typically, the keytab file is located at /etc/hadoop.keytab and the principal is in the form of hadoop/<hostname>@<REALM>.

    Note

    This workaround will be effective for the time period the Kerberos ticket is valid. This duration is 10 hours by default, but can configured by your Kerberos settings. You must re-run the above command once the Kerberos ticket expires.

  • When you use Spark with Hive partition location formatting to read data in Amazon S3, and you run Spark on Amazon EMR releases 5.30.0 to 5.36.0, and 6.2.0 to 6.9.0, you might encounter an issue that prevents your cluster from reading data correctly. This can happen if your partitions have all of the following characteristics:

    • Two or more partitions are scanned from the same table.

    • At least one partition directory path is a prefix of at least one other partition directory path, for example, s3://bucket/table/p=a is a prefix of s3://bucket/table/p=a b.

    • The first character that follows the prefix in the other partition directory has a UTF-8 value that’s less than than the / character (U+002F). For example, the space character (U+0020) that occurs between a and b in s3://bucket/table/p=a b falls into this category. Note that there are 14 other non-control characters: !"#$%&‘()*+,-. For more information, see UTF-8 encoding table and Unicode characters.

    As a workaround to this issue, set the spark.sql.sources.fastS3PartitionDiscovery.enabled configuration to false in the spark-defaults classification.

6.2.0 component versions

The components that Amazon EMR installs with this release are listed below. Some are installed as part of big-data application packages. Others are unique to Amazon EMR and installed for system processes and features. These typically start with emr or aws. Big-data application packages in the most recent Amazon EMR release are usually the latest version found in the community. We make community releases available in Amazon EMR as quickly as possible.

Some components in Amazon EMR differ from community versions. These components have a version label in the form CommunityVersion-amzn-EmrVersion. The EmrVersion starts at 0. For example, if open source community component named myapp-component with version 2.2 has been modified three times for inclusion in different Amazon EMR releases, its release version is listed as 2.2-amzn-2.

Component Version Description
aws-sagemaker-spark-sdk1.4.1Amazon SageMaker Spark SDK
emr-ddb4.16.0Amazon DynamoDB connector for Hadoop ecosystem applications.
emr-goodies3.1.0Extra convenience libraries for the Hadoop ecosystem.
emr-kinesis3.5.0Amazon Kinesis connector for Hadoop ecosystem applications.
emr-notebook-env1.0.0Conda env for emr notebook which includes jupyter enterprise gateway
emr-s3-dist-cp2.16.0Distributed copy application optimized for Amazon S3.
emr-s3-select2.0.0EMR S3Select Connector
emrfs2.44.0Amazon S3 connector for Hadoop ecosystem applications.
flink-client1.11.2Apache Flink command line client scripts and applications.
flink-jobmanager-config1.11.2Managing resources on EMR nodes for Apache Flink JobManager.
ganglia-monitor3.7.2Embedded Ganglia agent for Hadoop ecosystem applications along with the Ganglia monitoring agent.
ganglia-metadata-collector3.7.2Ganglia metadata collector for aggregating metrics from Ganglia monitoring agents.
ganglia-web3.7.1Web application for viewing metrics collected by the Ganglia metadata collector.
hadoop-client3.2.1-amzn-2Hadoop command-line clients such as 'hdfs', 'hadoop', or 'yarn'.
hadoop-hdfs-datanode3.2.1-amzn-2HDFS node-level service for storing blocks.
hadoop-hdfs-library3.2.1-amzn-2HDFS command-line client and library
hadoop-hdfs-namenode3.2.1-amzn-2HDFS service for tracking file names and block locations.
hadoop-hdfs-journalnode3.2.1-amzn-2HDFS service for managing the Hadoop filesystem journal on HA clusters.
hadoop-httpfs-server3.2.1-amzn-2HTTP endpoint for HDFS operations.
hadoop-kms-server3.2.1-amzn-2Cryptographic key management server based on Hadoop's KeyProvider API.
hadoop-mapred3.2.1-amzn-2MapReduce execution engine libraries for running a MapReduce application.
hadoop-yarn-nodemanager3.2.1-amzn-2YARN service for managing containers on an individual node.
hadoop-yarn-resourcemanager3.2.1-amzn-2YARN service for allocating and managing cluster resources and distributed applications.
hadoop-yarn-timeline-server3.2.1-amzn-2Service for retrieving current and historical information for YARN applications.
hbase-hmaster2.2.6-amzn-0Service for an HBase cluster responsible for coordination of Regions and execution of administrative commands.
hbase-region-server2.2.6-amzn-0Service for serving one or more HBase regions.
hbase-client2.2.6-amzn-0HBase command-line client.
hbase-rest-server2.2.6-amzn-0Service providing a RESTful HTTP endpoint for HBase.
hbase-thrift-server2.2.6-amzn-0Service providing a Thrift endpoint to HBase.
hcatalog-client3.1.2-amzn-3The 'hcat' command line client for manipulating hcatalog-server.
hcatalog-server3.1.2-amzn-3Service providing HCatalog, a table and storage management layer for distributed applications.
hcatalog-webhcat-server3.1.2-amzn-3HTTP endpoint providing a REST interface to HCatalog.
hive-client3.1.2-amzn-3Hive command line client.
hive-hbase3.1.2-amzn-3Hive-hbase client.
hive-metastore-server3.1.2-amzn-3Service for accessing the Hive metastore, a semantic repository storing metadata for SQL on Hadoop operations.
hive-server23.1.2-amzn-3Service for accepting Hive queries as web requests.
hudi0.6.0-amzn-1Incremental processing framework to power data pipline at low latency and high efficiency.
hudi-presto0.6.0-amzn-1Bundle library for running Presto with Hudi.
hudi-prestosql0.6.0-amzn-1Bundle library for running PrestoSQL with Hudi.
hudi-spark0.6.0-amzn-1Bundle library for running Spark with Hudi.
hue-server4.8.0Web application for analyzing data using Hadoop ecosystem applications
jupyterhub1.1.0Multi-user server for Jupyter notebooks
livy-server0.7.0-incubatingREST interface for interacting with Apache Spark
nginx1.12.1nginx [engine x] is an HTTP and reverse proxy server
mxnet1.7.0A flexible, scalable, and efficient library for deep learning.
mariadb-server5.5.64+MariaDB database server.
nvidia-cuda10.1.243Nvidia drivers and Cuda toolkit
oozie-client5.2.0Oozie command-line client.
oozie-server5.2.0Service for accepting Oozie workflow requests.
opencv4.4.0Open Source Computer Vision Library.
phoenix-library5.0.0-HBase-2.0The phoenix libraries for server and client
phoenix-query-server5.0.0-HBase-2.0A light weight server providing JDBC access as well as Protocol Buffers and JSON format access to the Avatica API
presto-coordinator0.238.3-amzn-1Service for accepting queries and managing query execution among presto-workers.
presto-worker0.238.3-amzn-1Service for executing pieces of a query.
presto-client0.238.3-amzn-1Presto command-line client which is installed on an HA cluster's stand-by masters where Presto server is not started.
prestosql-coordinator343Service for accepting queries and managing query execution among prestosql-workers.
prestosql-worker343Service for executing pieces of a query.
prestosql-client343Presto command-line client which is installed on an HA cluster's stand-by masters where Presto server is not started.
pig-client0.17.0Pig command-line client.
r3.4.3The R Project for Statistical Computing
ranger-kms-server2.0.0Apache Ranger Key Management System
spark-client3.0.1-amzn-0Spark command-line clients.
spark-history-server3.0.1-amzn-0Web UI for viewing logged events for the lifetime of a completed Spark application.
spark-on-yarn3.0.1-amzn-0In-memory execution engine for YARN.
spark-yarn-slave3.0.1-amzn-0Apache Spark libraries needed by YARN slaves.
spark-rapids0.2.0Nvidia Spark RAPIDS plugin that accelerates Apache Spark with GPUs.
sqoop-client1.4.7Apache Sqoop command-line client.
tensorflow2.3.1TensorFlow open source software library for high performance numerical computation.
tez-on-yarn0.9.2The tez YARN application and libraries.
webserver2.4.41+Apache HTTP server.
zeppelin-server0.9.0-preview1Web-based notebook that enables interactive data analytics.
zookeeper-server3.4.14Centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services.
zookeeper-client3.4.14ZooKeeper command line client.

6.2.0 configuration classifications

Configuration classifications allow you to customize applications. These often correspond to a configuration XML file for the application, such as hive-site.xml. For more information, see Configure applications.

Reconfiguration actions occur when you specify a configuration for instance groups in a running cluster. Amazon EMR only initiates reconfiguration actions for the classifications that you modify. For more information, see Reconfigure an instance group in a running cluster.

emr-6.2.0 classifications
Classifications Description Reconfiguration Actions

capacity-scheduler

Change values in Hadoop's capacity-scheduler.xml file.

Restarts the ResourceManager service.

container-executor

Change values in Hadoop YARN's container-executor.cfg file.

Not available.

container-log4j

Change values in Hadoop YARN's container-log4j.properties file.

Not available.

core-site

Change values in Hadoop's core-site.xml file.

Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer.

docker-conf

Change docker related settings.

Not available.

emrfs-site

Change EMRFS settings.

Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer.

flink-conf

Change flink-conf.yaml settings.

Not available.

flink-log4j

Change Flink log4j.properties settings.

Not available.

flink-log4j-yarn-session

Change Flink log4j-yarn-session.properties settings.

Not available.

flink-log4j-cli

Change Flink log4j-cli.properties settings.

Not available.

hadoop-env

Change values in the Hadoop environment for all Hadoop components.

Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer.

hadoop-log4j

Change values in Hadoop's log4j.properties file.

Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer.

hadoop-ssl-server

Change hadoop ssl server configuration

Not available.

hadoop-ssl-client

Change hadoop ssl client configuration

Not available.

hbase

Amazon EMR-curated settings for Apache HBase.

Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts.

hbase-env

Change values in HBase's environment.

Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer.

hbase-log4j

Change values in HBase's hbase-log4j.properties file.

Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer.

hbase-metrics

Change values in HBase's hadoop-metrics2-hbase.properties file.

Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer.

hbase-policy

Change values in HBase's hbase-policy.xml file.

Not available.

hbase-site

Change values in HBase's hbase-site.xml file.

Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer.

hdfs-encryption-zones

Configure HDFS encryption zones.

This classification should not be reconfigured.

hdfs-env

Change values in the HDFS environment.

Restarts Hadoop HDFS ZKFC.

hdfs-site

Change values in HDFS's hdfs-site.xml.

Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs.

hcatalog-env

Change values in HCatalog's environment.

Restarts Hive HCatalog Server.

hcatalog-server-jndi

Change values in HCatalog's jndi.properties.

Restarts Hive HCatalog Server.

hcatalog-server-proto-hive-site

Change values in HCatalog's proto-hive-site.xml.

Restarts Hive HCatalog Server.

hcatalog-webhcat-env

Change values in HCatalog WebHCat's environment.

Restarts Hive WebHCat server.

hcatalog-webhcat-log4j2

Change values in HCatalog WebHCat's log4j2.properties.

Restarts Hive WebHCat server.

hcatalog-webhcat-site

Change values in HCatalog WebHCat's webhcat-site.xml file.

Restarts Hive WebHCat server.

hive

Amazon EMR-curated settings for Apache Hive.

Sets configurations to launch Hive LLAP service.

hive-beeline-log4j2

Change values in Hive's beeline-log4j2.properties file.

Not available.

hive-parquet-logging

Change values in Hive's parquet-logging.properties file.

Not available.

hive-env

Change values in the Hive environment.

Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore.

hive-exec-log4j2

Change values in Hive's hive-exec-log4j2.properties file.

Not available.

hive-llap-daemon-log4j2

Change values in Hive's llap-daemon-log4j2.properties file.

Not available.

hive-log4j2

Change values in Hive's hive-log4j2.properties file.

Not available.

hive-site

Change values in Hive's hive-site.xml file

Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin.

hiveserver2-site

Change values in Hive Server2's hiveserver2-site.xml file

Not available.

hue-ini

Change values in Hue's ini file

Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations.

httpfs-env

Change values in the HTTPFS environment.

Restarts Hadoop Httpfs service.

httpfs-site

Change values in Hadoop's httpfs-site.xml file.

Restarts Hadoop Httpfs service.

hadoop-kms-acls

Change values in Hadoop's kms-acls.xml file.

Not available.

hadoop-kms-env

Change values in the Hadoop KMS environment.

Restarts Hadoop-KMS service.

hadoop-kms-log4j

Change values in Hadoop's kms-log4j.properties file.

Not available.

hadoop-kms-site

Change values in Hadoop's kms-site.xml file.

Restarts Hadoop-KMS and Ranger-KMS service.

hudi-env

Change values in the Hudi environment.

Not available.

jupyter-notebook-conf

Change values in Jupyter Notebook's jupyter_notebook_config.py file.

Not available.

jupyter-hub-conf

Change values in JupyterHubs's jupyterhub_config.py file.

Not available.

jupyter-s3-conf

Configure Jupyter Notebook S3 persistence.

Not available.

jupyter-sparkmagic-conf

Change values in Sparkmagic's config.json file.

Not available.

livy-conf

Change values in Livy's livy.conf file.

Restarts Livy Server.

livy-env

Change values in the Livy environment.

Restarts Livy Server.

livy-log4j

Change Livy log4j.properties settings.

Restarts Livy Server.

mapred-env

Change values in the MapReduce application's environment.

Restarts Hadoop MapReduce-HistoryServer.

mapred-site

Change values in the MapReduce application's mapred-site.xml file.

Restarts Hadoop MapReduce-HistoryServer.

oozie-env

Change values in Oozie's environment.

Restarts Oozie.

oozie-log4j

Change values in Oozie's oozie-log4j.properties file.

Restarts Oozie.

oozie-site

Change values in Oozie's oozie-site.xml file.

Restarts Oozie.

phoenix-hbase-metrics

Change values in Phoenix's hadoop-metrics2-hbase.properties file.

Not available.

phoenix-hbase-site

Change values in Phoenix's hbase-site.xml file.

Not available.

phoenix-log4j

Change values in Phoenix's log4j.properties file.

Restarts Phoenix-QueryServer.

phoenix-metrics

Change values in Phoenix's hadoop-metrics2-phoenix.properties file.

Not available.

pig-env

Change values in the Pig environment.

Not available.

pig-properties

Change values in Pig's pig.properties file.

Restarts Oozie.

pig-log4j

Change values in Pig's log4j.properties file.

Not available.

presto-log

Change values in Presto's log.properties file.

Restarts Presto-Server (for PrestoDB)

presto-config

Change values in Presto's config.properties file.

Restarts Presto-Server (for PrestoDB)

presto-password-authenticator

Change values in Presto's password-authenticator.properties file.

Not available.

presto-env

Change values in Presto's presto-env.sh file.

Restarts Presto-Server (for PrestoDB)

presto-node

Change values in Presto's node.properties file.

Not available.

presto-connector-blackhole

Change values in Presto's blackhole.properties file.

Not available.

presto-connector-cassandra

Change values in Presto's cassandra.properties file.

Not available.

presto-connector-hive

Change values in Presto's hive.properties file.

Restarts Presto-Server (for PrestoDB)

presto-connector-jmx

Change values in Presto's jmx.properties file.

Not available.

presto-connector-kafka

Change values in Presto's kafka.properties file.

Not available.

presto-connector-localfile

Change values in Presto's localfile.properties file.

Not available.

presto-connector-memory

Change values in Presto's memory.properties file.

Not available.

presto-connector-mongodb

Change values in Presto's mongodb.properties file.

Not available.

presto-connector-mysql

Change values in Presto's mysql.properties file.

Not available.

presto-connector-postgresql

Change values in Presto's postgresql.properties file.

Not available.

presto-connector-raptor

Change values in Presto's raptor.properties file.

Not available.

presto-connector-redis

Change values in Presto's redis.properties file.

Not available.

presto-connector-redshift

Change values in Presto's redshift.properties file.

Not available.

presto-connector-tpch

Change values in Presto's tpch.properties file.

Not available.

presto-connector-tpcds

Change values in Presto's tpcds.properties file.

Not available.

prestosql-log

Change values in Presto's log.properties file.

Restarts Presto-Server (for PrestoSQL)

prestosql-config

Change values in Presto's config.properties file.

Restarts Presto-Server (for PrestoSQL)

prestosql-password-authenticator

Change values in Presto's password-authenticator.properties file.

Restarts Presto-Server (for PrestoSQL)

prestosql-env

Change values in Presto's presto-env.sh file.

Restarts Presto-Server (for PrestoSQL)

prestosql-node

Change values in PrestoSQL's node.properties file.

Not available.

prestosql-connector-blackhole

Change values in PrestoSQL's blackhole.properties file.

Not available.

prestosql-connector-cassandra

Change values in PrestoSQL's cassandra.properties file.

Not available.

prestosql-connector-hive

Change values in PrestoSQL's hive.properties file.

Restarts Presto-Server (for PrestoSQL)

prestosql-connector-jmx

Change values in PrestoSQL's jmx.properties file.

Not available.

prestosql-connector-kafka

Change values in PrestoSQL's kafka.properties file.

Not available.

prestosql-connector-localfile

Change values in PrestoSQL's localfile.properties file.

Not available.

prestosql-connector-memory

Change values in PrestoSQL's memory.properties file.

Not available.

prestosql-connector-mongodb

Change values in PrestoSQL's mongodb.properties file.

Not available.

prestosql-connector-mysql

Change values in PrestoSQL's mysql.properties file.

Not available.

prestosql-connector-postgresql

Change values in PrestoSQL's postgresql.properties file.

Not available.

prestosql-connector-raptor

Change values in PrestoSQL's raptor.properties file.

Not available.

prestosql-connector-redis

Change values in PrestoSQL's redis.properties file.

Not available.

prestosql-connector-redshift

Change values in PrestoSQL's redshift.properties file.

Not available.

prestosql-connector-tpch

Change values in PrestoSQL's tpch.properties file.

Not available.

prestosql-connector-tpcds

Change values in PrestoSQL's tpcds.properties file.

Not available.

ranger-kms-dbks-site

Change values in dbks-site.xml file of Ranger KMS.

Restarts Ranger KMS Server.

ranger-kms-site

Change values in ranger-kms-site.xml file of Ranger KMS.

Restarts Ranger KMS Server.

ranger-kms-env

Change values in the Ranger KMS environment.

Restarts Ranger KMS Server.

ranger-kms-log4j

Change values in kms-log4j.properties file of Ranger KMS.

Not available.

ranger-kms-db-ca

Change values for CA file on S3 for MySQL SSL connection with Ranger KMS.

Not available.

spark

Amazon EMR-curated settings for Apache Spark.

This property modifies spark-defaults. See actions there.

spark-defaults

Change values in Spark's spark-defaults.conf file.

Restarts Spark history server and Spark thrift server.

spark-env

Change values in the Spark environment.

Restarts Spark history server and Spark thrift server.

spark-hive-site

Change values in Spark's hive-site.xml file

Not available.

spark-log4j

Change values in Spark's log4j.properties file.

Restarts Spark history server and Spark thrift server.

spark-metrics

Change values in Spark's metrics.properties file.

Restarts Spark history server and Spark thrift server.

sqoop-env

Change values in Sqoop's environment.

Not available.

sqoop-oraoop-site

Change values in Sqoop OraOop's oraoop-site.xml file.

Not available.

sqoop-site

Change values in Sqoop's sqoop-site.xml file.

Not available.

tez-site

Change values in Tez's tez-site.xml file.

Restart Oozie.

yarn-env

Change values in the YARN environment.

Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer.

yarn-site

Change values in YARN's yarn-site.xml file.

Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer.

zeppelin-env

Change values in the Zeppelin environment.

Restarts Zeppelin.

zookeeper-config

Change values in ZooKeeper's zoo.cfg file.

Restarts Zookeeper server.

zookeeper-log4j

Change values in ZooKeeper's log4j.properties file.

Restarts Zookeeper server.