3. Known Issues

BUG-47666

SNMPv3 is not supported.

The SNMPv3 notification method is not supported.

BUG-41308

DataNode Fails to Install on RHEL/CentOS 7.

During cluster install, DataNode fails to install with the following error:

resource_management.core.exceptions.
Fail: Execution of '/usr/bin/yum -d 0 -e 0 -y install snappy-devel' returned 1.
Error: Package: snappy-devel-1.0.5-1.el6.x86_64 (HDP-UTILS-1.1.0.20)
           Requires: snappy(x86-64) = 1.0.5-1.el6
           Installed: snappy-1.1.0-3.el7.x86_64 (@anaconda/7.1)
               snappy(x86-64) = 1.1.0-3.el7
           Available: snappy-1.0.5-1.el6.x86_64 (HDP-UTILS-1.1.0.20)
               snappy(x86-64) = 1.0.5-1.el6        

Hadoop requires the snappy-devel package that is a lower version that what is on the machine already. Run the following on the host and retry.

yum remove snappy
yum install snappy-devel            

BUG-41009

Static view instances throw a NullPointerException when attempting to access the view.

If you use a static <instance> in your view, you will receive a NullPointerException in ambari-server.log when attempting to use the view. You must instead use a dynamic view instance. Remove the static <instance> from your view.xml.

After upgrading from HDP 2.1 and restarting Ambari, the Admin > Stack and Versions > Versions tab does not show in Ambari Web.

After performing an upgrade from HDP 2.1 and restarting Ambari Server and the Agents, if you browse to Admin > Stack and Versions in Ambari Web, the Versions tab does not display. Give all the Agent hosts in the cluster a chance connect to Ambari Server by wait for Ambari to show the Agent heartbeats as green and then refresh your browser.

After adding Falcon to your cluster, the Oozie configuration is not properly updated.

After adding Falcon to your cluster using "Add Service", the Oozie configuration is not properly updated. After completion of Add Service wizard, add properties on Services > Oozie > Configs > Advanced > Custom oozie-site. The list of properties can be found here: https://github.com/apache/ambari/blob/branch-2.1/ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/configuration/oozie-site.xml. Once added, Restart Oozie and execute this command on oozie server host:

su oozie -c '/usr/hdp/current/oozie-server/bin/oozie-setup.sh prepare-war'

Start Oozie.

Accumulo Master Start fails on secure cluster if pid and log directories for YARN and MapReduce2 are customized.

If you plan to use Accumulo and a Kerberos-enabled cluster, do not customize the pid and log directories for YARN or MapReduce2.

Storm has no metrics if service is installed via a Blueprint.

The following properties need to be added to storm-site. Browse to Services > Storm > Configs and add the following properties. Restart the Storm service.

topology.metrics.consumer.register=
[{'class': 'org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsSink'
, 'parallelism.hint': 1}]
metrics.reporter.register=
org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter

If you cluster includes Accumulo and you disabled Kerberos, Accumulo tracer will fail to start with the following error:

resource_management.core.exceptions.Fail: Execution of 'cat /var/lib/ambari
-agent/data/tmp/pass | ACCUMULO_CONF_DIR=/usr/hdp/current/accumulo
-tracer/conf/server /usr/hdp/current/accumulo-client/bin/accumulo shell -u root -f
/var/lib/ambari-agent/data/tmp/cmds' returned 1. Password: *****
2015-07-04 05:08:44,823 [trace.DistributedTrace] INFO : SpanReceiver
org.apache.accumulo.tracer.ZooTraceClient was loaded successfully.
2015-07-04 05:08:44,897 [shell.Shell] ERROR:
org.apache.accumulo.core.client.AccumuloSecurityException: Error BAD_CREDENTIALS 
for user root - Username or Password is Invalid

To correct this situation, the following command must be run on one of the hosts that has an Accumulo process:

ACCUMULO_CONF_DIR=/etc/accumulo/conf/server accumulo init --reset-security 
--user root

It will prompt for the root user's password. The password you enter must match the Accumulo root password in Ambari's configs for Accumulo. Then Accumulo may be started normally.

When enabling Kerberos, Kafka security configuration is set and all the ZooKeeper nodes in Kafka will have ACLs set so that only Kafka brokers can modify entries in ZooKeeper. If you disable Kerberos, you user must set all the Kafka ZooKeeper entries to world readable/writable prior to disabling Kerberos. Before disabling kerberos for Kafka. Log-in as user "kafka" on one of Kafka nodes:

kinit -k -t /etc/security/keytabs/kafka.service.keytab kafka/_HOST

where _HOST should be replaced by the hostname of that node. Run the following command to open zookeeper shell:

/usr/hdp/current/kafka-broker/bin/zookeeper-shell.sh hostname:2181

where hostname here should be replaced by one of the zookeeper nodes

setAcl /brokers world:anyone:crdwa 
setAcl /config world:anyone:crdwa 
setAcl /controller world:anyone:crdwa 
setAcl /admin world:anyone:crdwa

If the above commands do not run prior to disabling Kerberos, the only option is to set "zookeeper.connect property" to a new ZooKeeper root. This can be done by appending "/newroot" to "zookeeper.connect.property" string. For example "host1:port1,host2:port2,host3:port3/newroot"

Falcon Service Check may fail when performing Rolling Upgrade, 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, :
 java.lang.NegativeArraySizeException
 at
 org.apache.kahadb.journal.DataFileAccessor.readRecord(DataFileAccessor.java:94)

This condition is rare.

When performing a Rolling Upgrade from HDP 2.2 to HDP 2.3 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.

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

After switching RegionServer ports, Ambari will report RegionServers are live and dead.

HBase maintains the list of dead servers and live servers according to it's semantics. Normally a new server coming up again with the same port will cause the old server to be removed from the dead server list. But due to port change, it will stay in that list for ~2 hours. If the server does not come at all, it will still be removed from the list after 2 hours. Ambari will alert, based on that list until the RegionServers are removed from the list by HBase.

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.

When Wire Encryption is enabled, the Tez View cannot connect to ATS with a Local Cluster configuration.

When running Ambari Server as non-root, when enabling Kerberos, if kadmin fails to authenticate, you will see the following error in ambari-server.log if Ambari cannot access the kadmind.log.

STDERR: Couldn't open log file /var/log/kadmind.log: Permission denied 
kadmin: GSS-API (or Kerberos) error while initializing kadmin interface

To avoid this error, be sure the kadmind.log file has 644 permissions.

User Views (Files, Hive and Pig) fail to load when accessing a Kerberos-enabled cluster.

You must specify a different directory for LevelDB (which is embedded in the ATS component) to use when generating temporal info. This can be done by adding the following information to the hadoop-env.sh configuration:

export JAVA_LIBRARY_PATH="${JAVA_LIBRARY_PATH}:/tktest"
export _JAVA_OPTIONS= "${_JAVA_OPTIONS} -Djava.io.tmpdir=/tktest"

With a Kerberos-enabled cluster that includes Storm, in Ambari Web > Services > Storm, the Summary values for Slots, Tasks, Executors and Topologies show as "n/a". Ambari Server log also includes the following ERROR:

24 Mar 2015 13:32:41,
288 ERROR [pool-2-thread-362] 
AppCookieManager:122 - 
SPNego authentication failed,
cannot get hadoop.auth cookie for URL: 
http: //c6402.ambari.apache.org:8744/api/
v1/topology/summary?field=topologies

When Kerberos is enabled, Storm API requires SPNEGO authentication. Refer to the Ambari Security Guide to Set Up Ambari for Kerberos to enable Ambari to authenticate against the Storm API via SPNEGO.

You must first create your cluster (via Install Wizard or via Blueprints) and then add Ranger service to the cluster.

When using an Agent non-root configuration, if you attempt to register hosts automatically using SSH, the Agent registration will fail.

The option to automatically register hosts with SSH is not supported when using a Agent non-root configuration. You must manually register the Agents.

When adding client-only services to a cluster (using Add Service), Ambari does not automatically install dependent client components with the newly added clients. On hosts where client components need to be installed, browse to Hosts and to the Host Details page. Click + Add and select the client components to install on that host.

If you attempt to rename a cluster to a string > 100 chars, Ambari Server will hang. Restart Ambari Server to clear the hang.