[OOZIE-2465] CoordActionCheckXCommand acquires lock on coord action id

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Assignee: Unassigned
• Reporter: Purshotam Shah
• Created: 23/Feb/16 20:11
• Updated: 28/Mar/19 10:53
• Resolved: 28/Mar/19 10:53

Description

@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));
						......

Only CoordActionCheckXCommand acquire lock on action id. All other action command acquires job id. This can cause race condition.

Issue Links

• relates to: OOZIE-2661 Coordinator Action status not updated when workflow job SUSPENDED