Known Issues and Workarounds in Cloudera Navigator Data Management

The sections below provide information about current known issues in Cloudera Navigator data management component.

Access or Login

Internet Explorer 11 document mode issue

When using Microsoft Internet Explorer 11 to access the Cloudera Navigator console, the login page does not display properly due to an issue with that browser's Compatibility View and certain document modes (see the Microsoft Technet article for details). As of Cloudera Navigator 2.10.1, a warning prompt now displays if the Internet Explorer's document mode is set to IE7 or lower, to alert you to the issue, but prior releases display a blank page rather than the login page.

Workaround: Open the Compatibility View Settings (under the Internet Explorer options menu) and remove the setting for the domain or website. Or use another browser to access the Cloudera Navigator console. Supported browsers include Mozilla Firefox, Google Chrome, or Microsoft Edge.

Error message ("not authorized") when logging in

The Cloudera Navigator console saves the state of the last URL accessed when you log out, and opens the same page at your next login. If two different users log in to Navigator using the same browser tab, the state of the first user applies to the second. If the second user does not have permissions to that section of the page, that user receives an error message.

Workaround: Close the browser tab and log in on a new tab. The state is cleared, and the access error message does not appear.

AWS and Amazon S3

Navigator requires stable AWS credentials for accessing S3

After setting up access to Amazon S3 for Navigator with a particular set of AWS credentials, Navigator requires that any future changes to AWS credentials be from the same AWS account, to avoid raising errors from the Amazon SQS (Simple Queue Service which is used transparently by Navigator.) Although you can change AWS account credentials in the Cloudera Manager Admin Console, trying to use different credentials with Navigator raises errors and does not succeed.

Workaround: If a new key is provided to Navigator in Cloudera Manager, the key must belong to the same AWS account as the prior key.

Unnamed folders on Amazon S3 not extracted

Unnamed folders on Amazon S3 are not extracted by Navigator, but the content of the folders is extracted. For example, a top-level folder the top level folder in the bucket has no name (for example, /bucket//folder/file), it is extracted as /bucket/folder/file.

Implicit folders are not marked as deleted in Navigator

If an implicit folder is deleted in S3, it does not appear as deleted in Navigator.

Workaround: To prevent folders deleted in S3 from appearing in Navigator Search results, include implicit:false in the search query.

Inconsistencies in AWS can cause Navigator extraction to stop

Inconsistencies that occur in AWS (for example, due to eventual consistency) can delay Navigator extraction of S3 data. When Navigator detects an inconsistency, extraction may stop until the inconsistency is resolved in AWS. Navigator will retry at the next scheduled extraction.

Data Stewardship Dashboard

Counts displayed in Dashboard and Search may differ

Counts for databases, tables, views, and other entities displayed in Cloudera Navigator Dashboard can differ from Search values for the same objects. The Dashboard displays data from the Navigator Audit Server, which contains actual counts captured continuously. On the other hand, Search (Solr) returns data that has been periodically extracted from HMS (Hive Metadata Server). Tables, databases, views, or other objects created or destroyed between extracts are not reflected in values displayed by Search (Solr), but they are contained in the audit data displayed in the Dashboard.

Tables Populated count reflects INSERT and UPDATE statements

The Tables Populated display widget in the Data Stewardship Dashboard reflects the number of times that a table has been loaded with data, such as through INSERT and UPDATE statements—not the number of unique tables loaded. For example, a single table to which data is added (through 6 INSERT statements) and that has also had 4 UPDATE statements submitted in the same period would report Tables Populated as 10.

Hive, Hue

Hive extractor limitations

The Hive extractor does not support all Hive statements, specifically these:

  • Table-generating functions
  • Lateral views
  • Transform clauses
  • Regular expressions (regex) in SELECT clause

Hive queries that include any of the above will prevent lineage diagrams from completing successfully.

Workaround: None.

Hive service configuration in auditing component

For Hive services, the auditing component does not support the "Shutdown" option for the "Queue Policy" property.

Severity: Low

Workaround: None.

Hue service audit log and Unknown IP address

The IP address in a Hue service audit log displays as "unknown".

Severity: Low

Workaround: None.

Hive and Hue services audit re-configurations require restart

Whenever a change is made to a Hive service's audit configuration, Beeswax must be restarted so that the Hue service audit log can reflect the change.

Severity: Low

Workaround: None.

Navigator Metadata Server

Metadata Server log file and spurious error messages

Certain configuations of OS and database (such as PostgreSQL and Ubuntu Linux) may raise spurious error messages regarding non-existent files. Such messages can be safely disregarded, such as this example:
Error: [main]: PWC6351: In TLD scanning, the
supplied resource file:/usr/share/java/oracle-connector-java.jar does not
exist.

Purge

Policy specifications and cluster names affect purge

Policies cannot use cluster names in queries. Cluster name is a derived attribute and cannot be used as-is.

Workaround: When setting move actions for Cloudera Navigator, if there is only one cluster known to the Navigator instance, remove the clusterName clause.

If there is more than one cluster known to the Navigator instance, replace clusterName with sourceId. To get the sourceId, issue a query in this format:
curl '<nav-url>/api/v9/entities/?query=type%3Asource&limit=100&offset=0'
Use the identity of the matching HDFS service for this cluster as the sourceId.

Purge appears suspended while extraction is running

When you issue a purge command, it does not start if extractors are running. During this time, the maintenance page indicates that maintenance tasks are not running. Once the extraction is complete and purge starts, it shows the status of the purge operations.

Spark

Spark Lineage Limitations and Requirements

Spark lineage diagrams are supported in the Cloudera Manager 5.11/Cloudera Navigator 2.10 release. Spark lineage is supported for Spark 1.6 only, not Spark 2.0 or 2.1. Lineage is not available for Spark when Cloudera Manager is running in single user mode. In addition to these requirements, Spark lineage has the following limitations:
  • Lineage is produced only for data that is read/written and processed using the Dataframe and SparkSQL APIs. Lineage is not available for data that is read/written or processed using Spark's RDD APIs.
  • Lineage information is not produced for calls to aggregation functions such as groupBy().
  • The default lineage directory for Spark on Yarn is /var/log/spark/lineage. No process or user should write files to this directory—doing so can cause agent failures. In addition, changing the Spark on Yarn lineage directory has no effect: the default remains /var/log/spark/lineage.

Spark extractor enabled using safety valve deprecated

The Spark extractor included prior to CDH 5.11 and enabled by setting the safety valve, nav.spark.extraction.enable=true is being deprecated, and could be removed completely in a future release. If you are upgrading to CDH 5.11 from a deployment that had configured this safety valve, be sure to remove the setting when you upgrade.

Upgrade Issues and Limitations

Issues and limitations matrix by release

Before upgrading Cloudera Navigator, review these version-specific release notes:

Upgrade Limitations, requirements, preliminary tasks
From... To...
2.10 2.10.1 Upgrading Cloudera Manager 5.11.0 to Cloudera Manager 5.11.1 results in failures by Navigator Audit Server to publish to Kafka. See Publishing to Kafka fails after upgrade for details and a workaround.
2.8 (and lower) 2.9 (and higher) Upgrading to Cloudera Navigator 2.9 can take a significant amount of time, depending on the size of the datadir. Before starting to upgrade to Cloudera Manager 5.10 (which automatically starts the upgrade to Cloudera Navigator 2.9), see Upgrading to Cloudera Navigator 2.9 Can be Extremely Slow. Briefly, in this release Solr indexing has been optimized to improve search speed. When the upgrade process completes and Cloudera Navigator services re-start, the Solr indexing upgrade automatically begins. No other actions can be performed until Solr indexing completes (progress message display during this process).
2.6 (and lower) Any The Cloudera Navigator Metadata Server requires an upgrade of data in the storage directory. See Upgrading Cloudera Navigator for details.
Any 2.4 – 2.6 Cloudera Navigator 2.4 – 2.6 do not support JDK 1.6, so upgrade any instances of JDK 1.6 to JDK 1.7 or 1.8 before upgrading to these releases. See Java Development Kit Installation for details.
2.1 2.2 Cloudera Navigator 2.1 used the beta version of the Navigator Metadata Server policy engine. Policies created using that version are not retained during the upgrade.
2.0 (and lower) 2.1 (and higher) The upgrade wizard for this upgrade path adds the Navigator Metadata Server to the Cloudera Manager cluster. The Navigator Metadata Server is new, and is not the same as the existing Navigator Audit Server database.
1.2 2.0 Cloudera Navigator 1.2 and Cloudera Navigator 2.0 have reached EOL (end of life) status and are no longer supported. There is no wizard for this upgrade path. Cloudera Navigator 2.0 required a clean install. The Navigator 1.2 Navigator Metadata Server was a beta release included with Cloudera Manager 5.0. The 1.2 version of the Navigator Metadata Server role must be removed before the cluster can be upgraded to Cloudera Navigator 2.0 (the roles are not compatible).