Known Limitations
This section consists of known limitations we are aware of, persisting in this release. These known limitations pertain to version 3.8.x.
- Issue: The MySQL JDBC URL used to connect to Hive does not include the required parameter allowPublicKeyRetrieval=true by default. This results in connection failures, especially when SSL is enabled on the Hadoop cluster. Workaround: Manually append allowPublicKeyRetrieval=true to the JDBC connection URL in the configuration.
- Issue: Hadoop service logs are not displayed in the Pulse UI if any one of the Elasticsearch pods is down, even when Elasticsearch is deployed on multiple VMs. This issue applies to Kubernetes-based Pulse deployments. Workaround: Ensure that all ElasticSearch pods are running and healthy to maintain consistent log visibility in the Pulse UI.
- When using the YARN Fair Scheduler, Pulse and Ambari may not capture statistics for jobs that complete in under 60 seconds
- For Standalone Spark 3.x.x, the number of actual waiting jobs might not match the waiting job count displayed in the Pulse UI.
- When performing a log search on the Logs page, the 'Source' field corresponds to
log.file.path, and the 'Services' field maps tofields.componentas 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 a 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.
Was this page helpful?