[OOZIE-3031] Coord job with only unresolved dependencies doesn't timeout

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 4.3.1
• Assignee: Purshotam Shah
• Reporter: Purshotam Shah
• Created: 11/Aug/17 23:34
• Updated: 14/Feb/18 13:02
• Resolved: 09/Oct/17 22:07

Description

CoordActionInputCheckXCommand.java

else if (!isTimeout(currentTime)) {
                if (!status) {
                    long addtionalDelay = isChangeInDependency ? 0
                            : ConfigurationService.getInt(CONF_COORD_INPUT_CHECK_REQUEUE_INTERVAL_ADDITIONAL_DELAY)
                                    * 1000L;
                    queue(new CoordActionInputCheckXCommand(coordAction.getId(), coordAction.getJobId()),
                            addtionalDelay + getCoordInputCheckRequeueInterval());
                }
                updateCoordAction(coordAction, isChangeInDependency);
            }
            else {
                if (!nonExistListStr.isEmpty() && isPushDependenciesMet) {
                    queue(new CoordActionTimeOutXCommand(coordAction, coordJob.getUser(), coordJob.getAppName()));
                }
                else {
                    // Let CoordPushDependencyCheckXCommand queue the timeout
                    queue(new CoordPushDependencyCheckXCommand(coordAction.getId()));
                }
                updateCoordAction(coordAction, isChangeInDependency);
            }
        }

!nonExistList Str.isEmpty() check is unnecessary, once the action has passed the timeout, it should be marked as timedout.

Issue Links

• is broken by: OOZIE-1976 Specifying coordinator input datasets in more logical ways