Acceldata
 ODP
Search documentation… ⌘K

Acceldata ODP 3.3.6.3-105 Hotfix Release Notes

This hotfix release introduces platform fixes and operational improvements that enhance upgrade reliability, service availability, and configuration management across the Acceldata Open Source Data Platform (ODP).

This release is built on ODP 3.3.6.3-104.

Key Highlights

Improved Upgrade Reliability

This release resolves several issues that could occur during platform upgrades, resulting in a more reliable upgrade experience and reducing the need for manual post-upgrade intervention.

The following improvements are included:

  • HBase logging restoration
    • Fixed an issue where the log4j2.properties file was not generated during upgrades, causing HBase Master and RegionServer logging to stop after upgrading existing clusters.
    • Ambari now correctly provisions and manages the required logging configuration, ensuring that logging continues after the upgrade.
  • MapReduce Job History Server
    • Fixed an issue where the MapReduce Job History Server UI returned HTTP 500 errors after upgrade because of RFC6265 cookie validation failures.
    • The Job History Server now starts correctly, and historical job information is accessible after upgrade.
  • Pinot upgrade improvements
    • Fixed a Pinot Controller startup failure caused by an unnecessary dependency on the controller.hdfs.data.dir configuration.
    • Fixed Pinot Broker and Server startup failures when using Hadoop Deep Storage by automatically packaging the required Hadoop client libraries.
    • These fixes eliminate manual post-upgrade workarounds and improve service availability after upgrading from Pinot 1.3 to Pinot 1.4.

Repository Links

For details on accessing the Ambari and ODP stack links, see Accessing Acceldata Repositories.

HBase Configuration Management

HBase configuration management has been improved by removing hardcoded JVM heap settings from the HBase service startup scripts.

HBase Master and RegionServer now use the heap size values configured in Ambari, allowing administrators to update memory settings without modifying startup scripts.

Pinot Service Startup

The Pinot service startup sequence has been optimized by correcting the service dependency check order during deployment and startup.

This improvement increases service initialization reliability and provides a more consistent deployment experience.