2. Behavioral Changes

Ambari 2.1.0 introduces the following changes in behavior as compared to previous Ambari versions:


Table 1.4. Ambari 2.1.0 Behavioral Changes

Apache Jira

HWX Jira



AMBARI-9784 BUG-32201 JDK SupportAdded support for JDK 1.8 and removed support for JDK 1.6. You must upgrade to JDK 1.7 in your current Ambari before upgrading to Ambari 2.1.
AMBARI-9791 BUG-32223 OS Support Added support for RHEL/CentOS/Oracle Linux 7 and removed support for RHEL/CentOS/Oracle Linux 5. You must be running RHEL/CentOS/Oracle Linux 6 or 7 before upgrading to Ambari 2.1.
AMBARI-6646 RMP-3096 Rack Awareness Added support for HDFS Rack Awareness. If you currently configured HDFS for rack awareness using your own topology script, that configuration will stay in place. If you want to switch to use Ambari Rack Awareness features, you will need to update the HDFS net.topology.script.file.name property to use the Ambari-generated script: /etc/hadoop/conf/topology_script.py
AMBARI-10506 BUG-33967 SSL Client and Server ConfigurationAdded support for managing ssl-client and ssl-server HDFS configurations. If you are currently managing these files manually across the hosts in your cluster, you will need to migrate management to Ambari.
AMBARI-12258 BUG-40449

ambari-env.sh Backup

During Ambari upgrade, the existing ambari-env.sh file is overwritten and a backup copy of ambari-env.sh (with extension . rpmsave) is created. If you have manually modified ambari-env.sh (for example, to change Ambari Server heap), you will need to re-apply your changes to the new file.
AMBARI-10648 BUG-34434HeatmapsThe Ambari Web Dashboard > Heatmaps tab includes a list of all heatmaps available for the hosts and services in the cluster. In addition, each Service that has Heatmaps also include a Service > Heatmaps tab with the list of the heatmaps specific to that Service. For example, HDFS and YARN include a heatmaps tab under their respective Services.
AMBARI-9794 BUG-32000Config OrganizationThe new Guided Configs features changes the layout + controls of Service Configs for HDFS, YARN, Hive and HBase. Under the Service > Configs tab, you will see sub-tabs "Settings" and "Advanced". The Settings tab include the most commonly used configuration properties for that service. The Advanced tab includes all other properties (with a layout similar to previous Ambari releases), including the Custom sections where you can add custom properties to a service configuration.
AMBARI-10400BUG-34054Sudo UsageWhen Ambari Agents are configured to run as non-root, Ambari will use sudo to execute commands. Therefore, sudo must be available in order to run non-root Agents. If you are not running a non-root Agent configuration, sudo will not be used to execute commands.
  Removed SLES 11 SP1 support.SLES 11 SP1 or SP3 can be used with Ambari when installing and managing HDP 2.2, 2.1 or 2.0 clusters. SLES 11 SP1 cannot be used with Ambari installing and managing HDP 2.3. You must use SLES 11 SP3.
  Ubuntu and Debian SupportAmbari 2.1.0 does not support Ubuntu 12.0.4, Ubuntu 14.0.4 or Debian 7; Hortonworks will add support for Ubuntu 12.0.4, Ubuntu 14.0.4 and Debian 7 in a later Ambari 2.1 maintenance release. If Ubuntu is critical to your environment today, do not use Ambari 2.1 and instead use Ambari 2.0.1 or a later Ambari 2.0 maintenance release.
  HDP Stack SupportAmbari support for HDP 2.0 and HDP 2.1 is deprecated starting with Ambari 2.1 release. Support for these HDP Stacks will be removed in a future Ambari release.
  HDP 2.0 or HDP 2.1 UpgradeAmbari 2.1 does not support directly upgrading from HDP 2.0 or HDP 2.1 to HDP 2.3. In order to upgrade from HDP 2.0 or HDP 2.1, you must first upgrade to HDP 2.2 using either Ambari 1.7 or 2.0. Once completed, upgrade your current Ambari to Ambari 2.1. Then, leverage Ambari 2.1 to complete the upgrade from HDP 2.2 to HDP 2.3.