Atlas and Ranger Default Installation

During the service selection process of a new install, you will see multiple limited functionality warnings if Atlas, Ranger, and their dependent services are not selected for install.

Ambari UI uses Websocket to communicate with the Ambari Server

The Ambari UI now uses websocket to communicate with the Ambari Server. If you were using Ambari through a proxy like Nginx, Knox, or Apache HTTPD, ensure that that proxy is configured to proxy Websocket traffic. If this is not done, the Ambari Web UI will not update quickly and performance will be very sluggish.

Ambari Server & Log Search UI Changes

In Ambari 2.7, the Ambari Server UI look and feel has changed significantly. Additionally the Log Search UI has been significantly changed.

Ambari Server Setup SSO CLI

The ambari-server setup-sso command now includes a prompt to setup SSO for Ambari, Atlas, and Ranger.

KDC Admin host must use FQDN

As of Ambari 2.7.0, the KDC admin host value is expected to be the fully qualified domain name (FQDN) of the host where the KDC administration server is. Anytime before the stack upgrade is to occur, and if Kerberos is enabled, the user should ensure that the KDC admin host is set to a FQDN.

Keytab Regeneration

After upgrading to Ambari 2.7.0, clicking the Regenerate Keytabs button and selecting only to regenerate missing keytabs will regenerate all keytabs. This behavior will only happen the first time this operation is performed, all subsequent use of Regenerate Keytabs with only missing keytabs selected will behave as usual.

KDC Admin Credentials Needed During Stack Upgrade

When upgrading from HDP 2.6 to HDP 3.0, additional YARN components are added to the cluster. If your cluster has Kerberos enabled, the Ambari Server must be configured to store the KDC admin credentials so that the principals for these components can be created during the upgrade.

Patch Upgrades

Ambari 2.7.0 will not support using patch upgrades to upgrade from HDP-3.0.0 to HDP-3.0.x. This functionality will be enabled in Ambari 2.7.1

Blueprint Deletion

We no longer allow a DELETE operation to be performed on an existing Blueprint when a cluster deployment has completed with that Blueprint. In any other case, the DELETE is still allowed.

Version API Change

The default response to the /api/v1/clusters has been changed. Before Ambari 2.7, each clusters “version” would be reported in the response of this call by default. In Ambari 2.7, this “version” field is no longer included in the default response, but can be included in the response if the following query parameters are used “/api/v1/clusters?fields=Clusters/version”