Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Oozie Stuck in PREP - HDP 2.5.3

avatar
New Member

When running any jobs, that were previously working, the job goes to PREP state (after the Start). Jobs were previously working with no issue.

When running an Oozie Service check, the following is received.

13220-screen-shot-2017-03-03-at-115935-pm.png

We recently upgraded from 2.3.0 to 2.5.3 and the jobs ran for a couple of days with no issue then in the middle of the day the jobs started acting like this.

When on the phone with Hortonworks Tech Support, we did set oozie.service.AuthorizationService.security.enabled to false and it temporarily started working and then quit again.

We do have HA enabled, but any of the posts that I have found didn't fix the issue.

1 ACCEPTED SOLUTION

avatar
New Member

After further troubleshooting and the changing of properties (with no success), I took the last resort of deleting the Oozie service and setting up on a new DB.

For now everything is back to normal. Root cause I suspect is db corruption.

This StackOverflow post kind of led me to do the inevitable.

View solution in original post

3 REPLIES 3

avatar
Master Mentor

@Jesse Passwaters please share job.properties and workflow.xml files

avatar
New Member

Here are the 2 files. This is what is used when I run the service check which fails.

workflow.xml

jobproperties.txt

avatar
New Member

After further troubleshooting and the changing of properties (with no success), I took the last resort of deleting the Oozie service and setting up on a new DB.

For now everything is back to normal. Root cause I suspect is db corruption.

This StackOverflow post kind of led me to do the inevitable.