[
https://issues.apache.org/jira/browse/OOZIE-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892411#comment-13892411
]
Mona Chitnis commented on OOZIE-1687:
-------------------------------------
bq.
|| (bundleaction.getCoordId() != null && bundleaction.isTerminalStatus() &&
coordjob
.isTerminalStatus()))
Above condition in BundleStatusUpdateXCommand, will it not change a terminal
bundleaction to a nonterminal state?
In unit test
{code}
assertEquals(CoordinatorJobBean.Status.KILLED, action.getStatus());
{code}
action here is bundle action, compare it with bundle action status to be non
ambiguous (even though the string value is essentially same)
> Bundle can still be in RUNNINGWITHERROR status after bundle kill
> ----------------------------------------------------------------
>
> Key: OOZIE-1687
> URL: https://issues.apache.org/jira/browse/OOZIE-1687
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 4.0.0
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
> Fix For: trunk
>
> Attachments: OOZIE-1687-1.patch
>
>
> Race condition between StatusTransitService (does not acquire lock) and
> BundleKillCommand can leave a bundle action with pending=1 and terminal
> status.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
