[
https://issues.apache.org/jira/browse/OOZIE-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111425#comment-14111425
]
Robert Kanter commented on OOZIE-1831:
--------------------------------------
[~satish.mittal], [~rohini], The part of the patch where we removed the call to
{{verifyDBState();}} makes sense to me; but I'm not sure why the
{{postUpgradeTasksFor40}} method was added. It looks like it duplicates the
end of the {{postUpgradeTasks}} method. Why was this done? Don't we need to
do the other stuff from {{postUpgradeTasks}}?
> Oozie upgrade fails if workflow jobs are in running or suspended state
> ----------------------------------------------------------------------
>
> Key: OOZIE-1831
> URL: https://issues.apache.org/jira/browse/OOZIE-1831
> Project: Oozie
> Issue Type: Bug
> Components: tools
> Affects Versions: 4.1.0
> Reporter: Satish Mittal
> Assignee: Satish Mittal
> Fix For: 4.1.0
>
> Attachments: OOZIE-1831.patch.txt
>
>
> While upgrading oozie from 3.x to trunk, oozie upgrade fails if there any
> workflow jobs found in running or suspended state:
> {noformat}
> 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)
> {noformat}
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
