My Oracle Support Banner

Existing Workflow/Coordinator/Bundle Jobs Inaccessible from Hue after BDA 3.0.1/CDH 5.0.1 Upgrade from CDH 2.*/CDH 4.* (Doc ID 1906715.1)

Last updated on JUNE 08, 2022

Applies to:

Big Data Appliance Integrated Software - Version 3.0.1 and later
Linux x86-64

Symptoms

NOTE: In the images, examples and document that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 

After upgrading to BDA 3.0.1/CDH 5.0.1  from CDH 2.*/CDH 4.* Workflow/Coordinator/Bundle jobs existing prior to the upgrade do not show up.  Another symptom is that trying to view existing Workflow/Coordinator/Bundle Jobs from the Hue UI raises "server 500".  The "server 500" error can be resolved by following the steps documented in: Accessing Existing Workflow/Coordinator/Bundle Jobs from Hue Raises "server 500" after BDA 3.0.1/CDH 5.0.1 Upgrade from CDH 2.*/CDH 4.* (Doc ID 1906672.1).  After following the steps in: 1906672.1, some existing Oozie Workflows will show up, but not all.  The existing Workflows that do show up may be missing content.  Existing Coordinator jobs are present but frequency details need to be updated for CDH 5.0.1. 

Symptoms from the Hue UI

1. In the Hue UI navigate to Workflows > Editor


a) View workflows which existed before the upgrade. You can search for a particular workflow as well, In the example here the workflow is: owf-load-and-organize.


b) Select a workflow that existed prior to upgrade.  The content will be empty.

2. In the Hue UI navigate to Workflows > Editor > Coordinator > Select a Coordinator job that existed prior to upgrade

The result might be: Server Error (500) as below.  However this will not always be a symptom.  The Coordinator jobs may be visible.


Symptoms from the javascript console (Optional)

Note: The behavior/steps here differ by browser.  This is an option verification which can be skipped.

1. Open up one of the existing oozie workflow jobs from the Hue UI:  Workflows > Editor.  The example here uses: owf-load-and-organize.

2. Open up a javascript console.  The instructions may differ by browser.  In Firefox for example navigate to Tools > Web Developer > Web Console

3. Refresh the main browser and you should see a javascript error like:

x SyntaxError: JSON.parse: unexpected end of data

Note: You can select the "workflow" on the right as in the screenshot below:

4.Refresh the browser and replace the current URL (pointing to the workflow) as below.

Change: http://bdanode04.example.com:8888/oozie/edit_workflow/32#editWorkflow

To: http://bdanode04.example.com:8888/oozie/workflows?managed=true

 

5. The above step will bring up a JSON response.  Within that JSON response there should be field "data" with an empty string ("") as a value.

Symptoms observed in the hue database

From Node 3 of the cluster verify the empty data in the Hue database.

1. Select the hue database:

  

Cause

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
Symptoms
 Symptoms from the Hue UI
 Symptoms from the javascript console (Optional)
 Symptoms observed in the hue database
Cause
Solution
 Solution
 Verify the workflows are accessible
 Coordinator jobs
References

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