Upgrade: Known Issues

Finalize Upgrade Pre-Check” Step Fails During Stack Express Upgrade

Description: The “Finalize Upgrade Pre-Check” step may fail during stack express upgrade if Kafka add-ons (Cruise Control, Kafka Connect, Kafka MirrorMaker) are installed.

Workaround:

  • Remove all Kafka add-ons before starting the upgrade.
  • Proceed with the upgrade.
  • Reinstall compatible Kafka add-ons after upgrade completion (if required).

Upgrade Service Configs Step Fails

  • Workaround (Option 1): Run Ambari Upgrade Helper Script
Bash
Copy
  • Workaround (Option 2): Select "Ignore and proceed."

Below instructions are applied for ODP-3.3.6.1-1 related upgrades

Oozie Restart Fails with “No Port in URL” for Non-SSL Clusters

  • Stage: Post-Upgrade Validation / Service Restart

Error Observed:No Port in URLRoot Cause:

  • The configuration property oozie.https.enabled was newly introduced in 3.3.6.2-1.
  • For existing non-SSL clusters, this property is missing, causing Oozie to fail during startup.

Workaround:

  1. In Ambari, navigate to Configs → Oozie → Custom oozie-site.
  2. Add the following property:
Bash
Copy
  1. Restart the Oozie service.

Druid Shuts Down After Ambari Upgrade to 3.0.0

Description: After upgrading Ambari to 3.0.0, the Druid service may shut down or fail to start.

Root Cause: The existing druid-env configuration is incompatible with Ambari 3.0.0. Required environment variables are missing or not exported correctly during service startup.

Workaround / Fix: Update Advanced → druid-env → druid-env template with the following content:

Bash
Copy
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
  Last updated