Apache Ambari Release Notes
Also available as:

Known Issues

Ambari 2.4 has the following known issues, scheduled for resolution in a future release. Also, refer to the Ambari Troubleshooting Guide for additional information.

Table 1.8. Ambari 2.4 Known Issues

Apache Jira

HWX Jira





The Use RedHat Satellite/Spacewalk button does not work.

To use Satellite or Spacewalk server for HDP repository management:

  • On Ambari Server, run:

     -u <ambari_admin_user> -p <ambari_admin_password> -port <port_ambari_is_running_on>
     set <ambari_server_host_name> <cluster_name> cluster-env repo_suse_rhel_template
     "[{{repo_id}}-DISABLED]\nname={{repo_id}}-DISABLED\n{% if mirror_list %}mirrorlist={{mirror_list}}
     {% else %}baseurl={{base_url}}{% endif %}\n\npath=/\nenabled=0\ngpgcheck=0"
  • On all the nodes managed by Ambari, run:

    sed -i 's/enabled=1/enabled=0/g' /etc/yum.repos.d/HDP*.repo

The second command disables external repositories on the nodes that have already been provisioned.



After changing hadoop.proxyuser.knox.groups or hadoop.proxyuser.knox.hosts to access hive2 through knox, the following error message displays:

Error: Failed to validate proxy privilege of knox_dv for v999003 (state=08S01,code=0)

Restart the Hive service, so that it operates using these updated core-site configurations.



If you have Storm in your cluster and have Kerberos enabled, after Ambari 2.4 upgrade, the Storm summary page in Ambari Web does not show information and exceptions are logged.

24 Aug 2016 14:19:38,107 ERROR [ambari-metrics-retrieval-service-thread-2738] MetricsRetrievalService:421
 - Unable to retrieve metrics from http://hcube1-1n02.eng.hortonworks.com:8744/api/v1/cluster/summary.
 Subsequent failures will be suppressed from the log for 20 minutes.
java.io.IOException: Server returned HTTP response code: 500 for URL: 
 at sun.reflect.GeneratedConstructorAccessor228.newInstance(Unknown Source)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

You need to add the Ambari Server principal name to the Storm nimbus.admins property in Ambari Web > Services > Storm > Configs.



Filtering by Role on Users page in Ambari Admin Interface is slow with 1000+ users.

If you have 1000+ users from LDAP synchronized into Ambari and you attempt to filtering by Role on the Users page in Ambari Admin Interface, the results will be slow (potential 20 seconds). Reducing the number of users you have synchronized into Ambari is a way to improve this performance.



Apache Oozie requires a restart after an Atlas configuration update, but may not be included in the services marked as requiring restart in Ambari.

Select Oozie > Service Actions > Restart All to restart Oozie along with the other services.


If you add or remove ZooKeeper servers and you have Atlas in your cluster, you must update some Atlas properties.

If you are running Atlas in your cluster and make changes to ZooKeeper (adding or removing ZooKeeper server components), you must update the Atlas properties list below to make sure they reflect the list of ZooKeeper servers in the cluster. You can modify the following properties from Ambari Web > Services > Atlas > Configs:

Sample: node-test0.docker.nxa.io:2181,node-test2.docker.nxa.io:2181,node-test1.docker.nxa.io:2181

Sample: node-test1.docker.nxa.io:2181/infra-solr,node-test0.docker.nxa.io:2181/infra-solr,node-test2.docker.nxa.io:2181/infra-solr

Sample: node-test0.docker.nxa.io,node-test2.docker.nxa.io,node-test1.docker.nxa.io

Sample: node-test0.docker.nxa.io,node-test2.docker.nxa.io,node-test1.docker.nxa.io 


When toggling and saving the Hive service's "Enable Interactive Query" configuration, it's important to wait for the background operations associated with that change to complete before trying to toggle it once more. If you don't wait for background operations to complete and try to re-enable this feature it can cause some of the operations to fail resulting in configuration inconsistencies.

If such inconsistencies are observed then retry toggling and saving of the "Enabling Interactive Query" configuration and wait for all requests (background operations) to complete.



Falcon Service Check may fail when performing Rolling Upgrade or downgrade, with the following error:

2015-06-25 18:09:07,235 ERROR - [main:]
 ~ Failed to start ActiveMQ JMS Message Broker.
 Reason: java.io.IOException: Invalid location: 1:6763311, :
 java.lang.NegativeArraySizeException (BrokerService:528) 
 java.io.IOException: Invalid location: 1:6763311, :

This condition is rare.

When performing a Rolling Upgrade from HDP 2.2 to HDP 2.3 (or upgrade > dowgrade > upgrade) and Falcon Service Check fails with the above error, browse to the Falcon ActiveMQ data dir (specified in falcon properties file), remove the corrupted queues, and stop and start the Falcon Server.

rm -rf ./localhost
cd /usr/hdp/current/falcon-server 
su -l <FALCON_USER> 


After adding or deleting ZooKeeper Servers to an existing cluster, Service Check fails.

After adding or deleting ZooKeeper Servers to an existing cluster, Service Check fails due to conflicting zk ids. Restart ZooKeeper service to clear the ids.



The Slider view is not supported on a cluster with SSL (wire encryption) enabled. Only use the Slider view on clusters without wire encryption enabled. If it is required to run Slider on a cluster with wire encryption enabled, please contact Hortonworks support for further help.