My Oracle Support Banner

Existing Hue Oozie Coordinator Settings Are Not Saved When Edited on BDA V4.2/BDA V4.3 (Doc ID 2081726.1)

Last updated on DECEMBER 11, 2019

Applies to:

Big Data Appliance Integrated Software - Version 4.2.0 to 4.3.0 [Release 4.2 to 4.3]
Linux x86-64


On BDA V4.2 (CDH 5.4.0) Hue Oozie Coordinator settings for Concurrency and Throttle are not getting reflected in the coordinator.xml when changing an existing Coordinator job.  In the case of trying to change an existing Coordinator job and reset the Concurrency and Throttle to a value required, those values do not save, and even re-submitting the job sees no impact because the settings are not saved in the workflow. 

For example: On BDA V4.2 in the Hue Oozie Coordinator Editor setting the Concurrency parameter to for example '2' has the following unexpected result:
(Navigate: Hue Web UI > Oozie Editor > Coordinator > Concurrency = 2)

a) Concurrency does not remain at for example 2 and resets to default
b) The change to for example 2 is not reflected in the coordinator.xml after saving.

The parameter Throttle has the same issue:
a) Throttle does not remain at set value and resets to default
b) Changes are not reflected in the coordinator.xml after saving.

However, when a new Coordinator job is created for the workflow with the Concurrency and Throttle value set to the required values, they are saved and the job works upon re-submission.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.