[OOZIE-1831] Oozie upgrade fails if workflow jobs are in running or suspended state

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.1.0
• Fix Version/s: 4.1.0
• Component/s: tools
• Assignee: Satish Mittal
• Reporter: Satish Mittal
• Created: 12/May/14 18:48
• Updated: 09/Dec/14 00:45
• Resolved: 13/May/14 17:03

Description

While upgrading oozie from 3.x to trunk, oozie upgrade fails if there any workflow jobs found in running or suspended state:

Error: There are [26] workflows in RUNNING/SUSPENDED state, they must complete or be killed

Stack trace for the error was (for debug purposes):
--------------------------------------
java.lang.Exception: There are [26] workflows in RUNNING/SUSPENDED state, they must complete or be killed
	at org.apache.oozie.tools.OozieDBCLI.verifyDBState(OozieDBCLI.java:992)
	at org.apache.oozie.tools.OozieDBCLI.upgradeDB(OozieDBCLI.java:197)
	at org.apache.oozie.tools.OozieDBCLI.run(OozieDBCLI.java:128)
	at org.apache.oozie.tools.OozieDBCLI.main(OozieDBCLI.java:76)

This check seems unnecessary. It may not be possible to ensure in production that no workflows are in running/suspended state before upgrade.

Also current upgrade code updates the status of coord jobs/coord actions in DB. This may not be required now.