DocsHortonworks Data Platform

 

 4. Known Issues

In this section:

  • Ambari does not support running or installing stacks on Ubuntu.

  • The component version information displayed by Ambari is based on the Ambari Stack definition. If you have applied patches to the Stack and to your software repository, that component version might differ from the actual version installed. There is no functional impact on Ambari if the patch versions mismatch. If you have any questions on component versions, refer to the rpm version installed on the actual host.

  • BUG-24234: Unable to start/stop services when using Oracle database for Ambari.

    Problem: If you are using Oracle for the Ambari DB, you can run into a scenario when performing a start all/stop all where Ambari becomes unresponsive and the following ORA error is printed to the ambari-server log:

    08:54:51,320 ERROR [qtp1280560314-2070] ReadHandler:84 - Caught a runtime exception executing a query
Local Exception Stack: 
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.4.0.v20120608-r11652): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLSyntaxErrorException: ORA-01795: maximum number of expressions in a list is 1000

    Workaround: Please upgrade to Ambari 1.6.1 and contact Hortonworks Support for a patch to apply.

  • BUG-16783: Default MySQL max allowed packet size setting too small.

    Problem: When using MySQL for Ambari DB and enabling Kerberos Security on the cluster, you receive a persistence exception "Packet for query is too large".

    Workaround: Increase the max_allowed_packet setting in MySQL from the default 1M to 128M. This can accomplished with the following steps:

    1. Modify the MySQL configuration file /etc/my.cnf on the MySQL server host.

    2. Add the following entry: 

      [mysqld] max_allowed_packet=128M

    3. Save and restart MySQL server.

  • BUG-16729, AMBARI-5472: MySQL database installed by Ambari does not work with streaming ingest.

    Problem: When Ambari creates the metastore database in MySQL, it uses the DataNucleus auto create feature. This does not create the transaction tables, so any ACID operations (including streaming ingest) will not work.

    Workaround: After Ambari has created the mysql database, make the following changes: 

    mysql -u <dbuser> -D <dbname> -p < /usr/lib/hive/scripts/metastore/upgrade/mysql/hive-txn-schema-0.13.0.mysql.sql

    You will be asked for the password. <dbuser>, <dbname>, and the password can be found in /etc/hive/conf.server/hive-site.xml. javax.jdo.option.ConnectionUserName, value is user name javax.jdo.option.ConnectionURL, db name is the last element of the URL before the parameters, for example if your URL is jdbc:mysql://db.me.come/hivedb?createDatabaseIfNotExist=true, then your database name is "hivedb" javax.jdo.option.ConnectionPassword, value is the password.

  • BUG-16623, AMBARI-5509: "Check Falcon" failed after disabling security without first pre-configuring a kerberos cluster.

    Problem: Disabling security using Ambari is also disabling Falcon authentication.

  • BUG-16565: Hive and Storm do not start after changing of some ports.

    Problem: Hive and Storm services currently expect the default ports set by Ambari on install. Making changes to other ports causes the services to stop and makes them unable to restart.

    Workaround: Use the default ports for all services to ensure regular Hive and Storm service.

  • BUG-16556, AMBARI-5435: "Connection refused" errors in the YARN application logs. Timeline service is not started, but yarn-site.xml has the timeline-related configuration enabled.

    Problem: ATS is turned off in secure clusters installed by Ambari but in the yarn-site.xml, the ATS config is set to true. As a result, there are "Connection refused" errors in the YARN application logs.

    Workaround: Set yarn.timeline-service.enabled in yarn-site.xml to false:

    <property>
      <name>yarn.timeline-service.enabled</name>
      <value>false</value>
    </property>

  • BUG-16534: Quick links (Oozie Web UI, Falcon Web UI) do not work after reconfiguring port of oozie.base.url

    Description: This occurs because the Oozie HTTP port (11000) and Admin port (11001) cannot be changed via Ambari. Oozie uses 11001 as the default Admin port.

    Workaround: Reset ports to Oozie HTTP port (11000) and Admin port (11001).

Legal notices