Title
Create new category
Edit page index title
Edit category
Edit link
Known Limitations
This section consists of known limitations we are aware of, persisting in this release.
| Issue Description | Found in Version | Fixed in Version |
|---|---|---|
| The impala-kill-query action migration for CDP clusters is not supported. | 4.1.0 | |
| The duplicate region size data may appear in the HBase Table Details graph and downloaded reports. | 4.1.0 | |
A delay of approximately 2–3 minutes is observed between ClickHouse query completion and the results being displayed in the UI. For details about lowering the delay with a caution, see Query Listing Latency in Pulse. | 4.1.0 | |
| Tez Dashboard-The “Top 20 Tables by Query” chart values may not match the Tez → Tables listing page counts due to queue-level filtering being applied only at the dashboard level. | 3.6.0 and later | |
| Podman ReadOnlyRootFS Not Supported | 4.1.0 | |
| Pulse UI may respond slowly when incident volume grows beyond 50,000 records, especially if alerts generate incidents at very short intervals. | 4.1.0 | |
| In standalone Kafka setups with SSL enabled, the securityProtocol may be incorrectly set to SASL_PLAINTEXT instead of SASL_ SSL and requires manual correction in acceldata.conf. | 4.1.0 | |
| Flink application logs may not be available in Pulse for jobs running in application mode. | 4.1.0 | |
| Kafka3 (ODP) with SCRAM authentication fails with “Failed to create new NetworkClient” during connector initialization. | 4.1.0 | |
| Kafka3 MM2 dashboards show no data for Message Count and Topics Throughput/sec metrics in Pulse 4.1.x. | 4.1.0 | |
| On Kubernetes (replica count > 1), some MapReduce YARN applications may be missing from Pulse UI due to partition rebalancing issues affecting event consumption. | 4.1.0 | |
| Sorting on the Clusters column in the Roles page may not work correctly when multiple clusters are associated. | 4.1.0 | |
Issue: Search filters were not preserved when switching to “View Concurrency” on the YARN search page, causing inconsistent results. Workaround: Manually deselect and reapply the required search filters after using “View Concurrency.” | 4.1.0 | |
| The "~=" operator returned incorrect results on the Yarn Application Explorer RM Live View page. | 4.1.0 | |
| Clicking on “Show Anomaly Prediction” in the Druid Dashboard showed incorrect/duplicate messages indicating anomaly detection was not enabled. | 4.1.0 | |
| Duplicate data was displayed in the Region Size graph and downloaded file on the HBase Table Details page. | 4.1.0 | |
For the following actions, a separate Kerberos tile is not required:
These tiles already include Kerberos fields, which the user can fill in when the cluster is Kerberized. For all other actions where the is_kerberized option is present, a separate Kerberos tile should be shown. | 4.1.0 | |
| While editing roles, selecting “ALL” in Users and Roles does not consistently select all users/queues; administrators must manually choose the required users and queues when assigning permissions. | 4.1.0 | |
| Search performance may degrade significantly when querying datasets with more than 5 million records on the Query Listing page. | 4.1.0 | |
| The accelo deploy core command may fail due to streaming service issues when ReadOnlyRootFS is enabled in Podman, which is not currently supported. | 4.1.0 | |
| When you click Info icon on the HDFS dashboard does not display any information when clicked. Instead Instead hover over the icon to see the information. | 4.1.0 | |
| HBase table details may not display all regions under Region Details and Compaction, and store file data may be missing. | 4.1.0 | |
| The HDFS reports in Chargeback may be visible even when the user does not have HDFS permissions. | 4.1.0 | |
| The role creation considers components only from the currently active cluster instead of all selected clusters. | 4.1.0 | |
| The Spark component may appear in the side panel even when the user does not have permission for it. | 4.1.0 | |
| Pinot component may appear in the side panel even when the user does not have permission for it. | 4.1.0 | |
| Filtering by “Regions by State Count” graph in HBase Table Details may not work correctly. | 4.1.0 | |
| For Pulse on Kubernetes, data loss may occur if pods restart or scale down due to high usage or auto-scaling. | 4.1.0 | |
| The ad-events (NATS) service may become temporarily unreachable during pod autoscaling under high load (e.g., datagen on Hadoop nodes), requiring restart for recovery. This is applicable for Pulse on Kubernetes deployment only. | 4.1.0 | |
| Action logs may show a generic timeout reason (“please check if agents are running on the nodes”) instead of the actual failure cause. | 4.1.0 | |
| The action plugins may fail to register if the AXN agent starts before the AXN server is available; restarting the agent resolves the issue. Contact Acceldata Support if the problem persists. | 4.1.0 | |
| Spark job metrics (Avg Memory, Memory Time, Avg VCore, VCore Time) may appear intermittently due to delays in Elastic data availability or retry window limitations. | 4.1.0 | |
| The Service principal name is not enforced as a mandatory field on UI when configuring actions on Kerberized clusters. | 4.1.0 | |
| Some NATS streams may be created with a replication factor lower than the number of nodes in the NATS cluster. | 4.1.0 | |
| Spark DAG displayed in Pulse UI may not match the Spark UI and can show only the initial plan instead of the final execution plan for some queries. | 4.1.0 | |
| Airflow dataset statistics (e.g., orphaned datasets count) may be inaccurate and show incorrect values such as 0. | 4.1.0 | |
Running Workaround Manually update the script to enable Kerberos by setting | 4.0.2 | |
| Pulse currently supports only one Ozone Service ID; multi–service ID support is not yet available. | ||
| The DAG shown on the Pulse Spark Job Details page may miss some details compared to the Spark History Server DAG. | ||
| When you select Show Files Only on the HDFS File Explorer page, the sorting capability is not available for the Replicated Size column at the file level. | 4.0.1 | |
| (Applicable only to New Actions) When queries or applications are killed using the YARN kill action, the fields KilledByExecutionId and isKilled are not populated. Although the application is successfully terminated and visible in the YARN Application Explorer, these fields remain empty, impacting the ability to identify and audit killed queries. | 4.0.1 | |
| The Impala Kill action (New) requires a fully qualified coordinator URL (including protocol and port); hostname-only values are not supported. | 4.0.1 | |
| Spark job duration is calculated only after the job completes. As a result, any alerts for Spark based on job duration are evaluated and triggered post-completion, not while the job is running. | ||
| In the Impala Query Plan view, queries with a large number of nodes take a long time to load, showing incorrect results. | 4.0.0 | 4.0.1 |
| The dropdown filter on the Actions page might not work after a search filter is applied. | 4.0.0 | |
| The “Save Search” option is not available in the Logs view in the new UI. | 4.0.0 | |
| The filters applied on the Database page may not be reflected in the Table Usage by Query Count chart. | 4.0.0 | |
| In time-series charts, x-axis timestamp labels may overlap when there are large gaps between data points. | 4.0.0 | |
| In the HBase Dashboard, clicking a Regions by State Count graph does not apply the corresponding filter correctly in the search filter. | 4.0.0 | |
| Pulse will not be able to collect logs when the readonlyrootfs flag is enabled for Docker containers. | 4.0.0 | |
| Cluster-specific permissions are not applied correctly for LDAP users with multiple roles. When a user is assigned different roles across different clusters, Pulse allows users to access all the assigned permissions for each cluster. | 4.0.0 | |
| You might see an issue when importing alerts. Drag-and-drop may not work, and uploading through the file picker can result in errors. | 4.0.0 | |
| A Pulse user without any role would be able to access the Home, Incidents, Services, and Dashplots pages. These pages should be restricted, but access is granted even when the required role is not defined. | 4.0.0 | |
| The refresh buttons on charts do not update the charts with the latest data. Users can access the latest data by refreshing the browser window. | 4.0.0 | |
| In the YARN Application Explorer search, a long list of search options can appear truncated at the bottom, causing the dropdown to appear cut off. | 4.0.0 | |
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 tolog.file.path, and the 'Services' field maps to fields.component 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 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. |
Pulse on Kubernetes: Performance-Specific Known Limitations
Pulse runs reliably on Kubernetes. In certain scenarios, such as high workloads or resource constraints, you might notice performance impacts, including data loss, alert delays, POD restarts, etc. The following points describe these conditions and provide workarounds to help you maintain stability and performance.
| Issue Description | Found in Version | Fixed in Version |
|---|---|---|
PODs restart when data operations exceed allocated resources.
| 3.8.1 | |
Alert delays under POD failures or high workload:
| 3.8.1 | |
POD performance depends on the cluster and infrastructure
| 3.8.1 |
For additional help, contact www.acceldata.force.com OR call our service desk +1 844 9433282
Copyright © 2026