[OOZIE-1939] Incorrect job information is set while logging

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.2.0
• Assignee: seoeun
• Reporter: Purshotam Shah
• Created: 17/Jul/14 17:15
• Updated: 18/May/15 07:11
• Resolved: 18/Aug/14 06:27

Description

2014-07-16 17:28:06,422 DEBUG CoordChangeXCommand:545 [http-0.0.0.0-4443-5] - USER[hadoopqa] GROUP[users] TOKEN[] APP[coordB236] JOB[0011514-140716042555-oozie-oozi-C] ACTION[-] Acquired lock for [0011385-140716042555-oozie-oozi-C] in [coord_change]
2014-07-16 17:28:06,422 TRACE CoordChangeXCommand:548 [http-0.0.0.0-4443-5] - USER[hadoopqa] GROUP[users] TOKEN[] APP[coordB236] JOB[0011514-140716042555-oozie-oozi-C] ACTION[-] Load state for [0011385-140716042555-oozie-oozi-C]

    protected void loadState() throws CommandException {
        jpaService = Services.get().get(JPAService.class);
        if (jpaService == null) {
            LOG.error(ErrorCode.E0610);
        }

        try {
            coordJob = CoordJobQueryExecutor.getInstance().get(CoordJobQuery.GET_COORD_JOB_MATERIALIZE, jobId);
            prevStatus = coordJob.getStatus();
        }
        catch (JPAExecutorException jex) {
            throw new CommandException(jex);
        }

        // calculate start materialize and end materialize time
        calcMatdTime();

        LogUtils.setLogInfo(coordJob, logInfo);
    }

Most of the commands set jobinfo after loadstate, because of that few log statements ( like acquiring lock, load state) logs with previous jobinfo.

Issue Links

• links to: reviewboard