You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Andras Salamon (JIRA)" <ji...@apache.org> on 2019/03/28 10:54:00 UTC
[jira] [Resolved] (OOZIE-2465) CoordActionCheckXCommand acquires
lock on coord action id
[ https://issues.apache.org/jira/browse/OOZIE-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andras Salamon resolved OOZIE-2465.
-----------------------------------
Resolution: Duplicate
OOZIE-2661 fixed this.
> CoordActionCheckXCommand acquires lock on coord action id
> ---------------------------------------------------------
>
> Key: OOZIE-2465
> URL: https://issues.apache.org/jira/browse/OOZIE-2465
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
> Priority: Major
>
> {code}
> @Override
> public String getEntityKey() {
> return actionId;
> }
>
> protected Void execute() throws CommandException {
> .....
> LOG.debug("Updating Coordinator actionId :" + coordAction.getId() + "status to ="
> + coordAction.getStatus());
> coordAction.setLastModifiedTime(new Date());
> updateList.add(new UpdateEntry<CoordActionQuery>(CoordActionQuery.UPDATE_COORD_ACTION_STATUS_PENDING_TIME,
> coordAction));
> ......
> {code}
> Only CoordActionCheckXCommand acquire lock on action id. All other action command acquires job id. This can cause race condition.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)