Acceldata
 Pulse
Search documentation… ⌘K

Version 4.0.5

Release Date: 28th April, 2026

Important

To use the latest Pulse 4.0.5 version, you must upgrade your Docker version to 20.10.x or higher and perform the required migration steps. For more information, see Upgrade to Version 4.0.5.

Pulse supports N-2 to N versions during migration. For details, see Supported Pulse Upgrade Path.

Enhancements

  • Kafka 3 Authentication Support: Pulse now monitors Kafka 3 deployments configured with Multi-KDC and TLS/SSL, providing secure authentication and operational and performance insights. For details, see Configure Pulse to Monitor Standalone Kafka 3 > Answer the CLI Questions > Select the security type used by your Kafka cluster.
  • Standalone Kafka 3 (Kerberos) Monitoring Support: This release introduces monitoring for Standalone Kafka 3 with Kerberos, including TLS support, Zookeeper/KRaft metadata management, and improved configuration for connectors, JMX, and log ingestion. For details, see Configure Pulse to Monitor Standalone Kafka 3 with Kerberos.
  • Downloading Records:
    • The option to download records for components such as Tez queries, YARN applications, Spark Jobs, Impala queries, etc., from the Pulse UI in .xlsx format has been removed due to high memory consumption, which could impact the Pulse UI service performance.
    • You can continue to download the query results in .csv format, which is lighter and more efficient.
    • To enhance the stability during large export jobs, Pulse introduced a few system limitations for download job retention, job concurrency, lock lifetime, and compression level. These settings help reduce memory and CPU pressure during large exports and improve recovery for stuck jobs. For details, see System Limitations for Downloads Exceeding 10K Records.
  • xMatters Webhook Support (Configurable Endpoint & Payload): Added support for xMatters webhook configuration using the IS_WEBHOOK environment variable. This enables switching between the default generic webhook (/api/sendAlert) and a fully configurable xMatters-specific endpoint and payload format. For more information, see xMatters Notifications > xMatters Webhook Configuration (Pulse 4.0.5 or later).
  • Introduced a New Hook: Introduced a new hook version 2.0.1 for Pulse 4.0.x with improved compatibility. For details, see Supported Hook Versions.

Resolved Issues

Resolved Issues

This section consists of key issues that have been fixed in this release.

  • Fixed an issue where the HDFS Usage by User dashboard showed no data.
  • Fixed an issue where links in ‘Succeeded Action’ email alerts redirected to port 4000 instead of the correct SSL-enabled load balancer URL.
  • Fixed an issue where the HDFS File Explorer in Pulse showed incomplete directory structures and missing paths (such as /prod and /prod/archive) even after successful automated and manual fsimage loads.
  • Fixed an issue where the report generated for the custom dashboard created from the Dashplots is not sending the correct chart to the configured email address.
  • Resolved the Hive performance degradation issue caused by Tez hook failures (NATS client exceptions) when Pulse was down by removing the hook configurations.
  • Resolved the Spark job failures caused by NATS server dependency when Pulse was down by updating the Spark hook to handle NATS connectivity failures.
  • Resolved the issue where Tez queries remained in a Running state in Pulse UI after completion by fixing delayed/missed Tez event processing to correctly update query status.
  • Fixed an issue where MapReduce metrics were not displayed in the Pulse YARN Application Explorer UI page after job completion.
  • Resolved TEZ DAG query issue caused by Hive metastore incompatibility with HDP 2.6.x by fixing it in the ad-connector. Resolved the missing TEZ events issue caused by a hooks bug (NATS resolution) by updating to hooks version 2.0.1. Ensure to update the hook version.
  • Fixed an issue where the YARN Move Queue action failed due to outdated scripts, permission issues, and missing resourceRequests handling—resolved by updating the script with fallback logic (allocatedMB), correcting queue matching, and aligning configurations in the customer environment.
  • Fixed a file descriptor leak in the ad-director service that caused the number of open files to grow over time.
  • Resolved an issue where Oozie Workflow Jobs and Actions were not visible in Pulse UI due to checkpoint inconsistencies, non-deterministic query sorting, and Oracle CLOB/NCLOB serialization failures, ensuring reliable data ingestion and display across databases.