Known Limitations

This section consists of known limitations we are aware of, persisting in this release. These known limitations pertain to version 3.5.0.

The File Explorer page doesn’t load while the FSimage processing is in progress.
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.
The configured time might not work as expected sometimes for the scheduled actions.
When the Hydra service is down, the agent's status information is not available.
The Notifications capability is not working as expected if the Notification service is on a standalone node and ad-axnserver is on a core node.
Workaround:*

Add a mapping of the ad-notifications tag in the _ /etc/hosts_ file with the IP of the standalone node.
Mount this host's file in the ad-axnserver container. Then the notifications work as expected.

Last updated on

Was this page helpful?