Known Limitations

• When performing a log search on the Logs page, the 'Source' field corresponds to log.file.path, and the 'Services' field maps to [INLINE_CODE]fields.component[/INLINE_CODE] as defined in the database schema. Use these corresponding fields to fetch log details accurately.
• Changes made to the JDBC URL of the Oozie metastore in the acceldata.conf file does not persist after executing the acceldata reconfig cluster command.
• The MySQL JDBC URL for Oozie requires the allowPublicKeyRetrieval=true parameter, whereas it works without this parameter for Hive.
• When the multiple HDFS Paths Usage reaches the alert threshold, sometimes you might not receive notification for all paths.
• In a multi-cluster setup, a user can open only one cluster at a time, even when using different browser windows or tabs.
• Pulse does not support HBase version 2.5.8 at this time. You can use a compatible version for optimal functionality.
• The dashboard created using the elastic data source does not work when imported on a different cluster.
• The count of queries on the Impala Queries page and Impala Queries Details page might mismatch for the last 15 minutes in case of a larger number of queries.
• The vertex duration on the Tez page can be incorrect for some queries.
• The application logs for short-duration Yarn applications may not persist long enough for the log collector agent (Pulse Logs) to scrape. This may result in missing metrics (usedContainers) dependent on the parsed application logs.