You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Purshotam Shah (JIRA)" <ji...@apache.org> on 2014/07/17 19:19:04 UTC
[jira] [Updated] (OOZIE-1939) Incorrect job information is set
while logging
[ https://issues.apache.org/jira/browse/OOZIE-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Purshotam Shah updated OOZIE-1939:
----------------------------------
Description:
{code}
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]
{code}
{code}
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);
}
{code}
Most of the commands set jobinfo after loadstate, because of that few log statements ( like acquiring lock, load state) logs with previous jobinfo.
> Incorrect job information is set while logging
> ----------------------------------------------
>
> Key: OOZIE-1939
> URL: https://issues.apache.org/jira/browse/OOZIE-1939
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
>
> {code}
> 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]
> {code}
> {code}
> 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);
> }
> {code}
> Most of the commands set jobinfo after loadstate, because of that few log statements ( like acquiring lock, load state) logs with previous jobinfo.
--
This message was sent by Atlassian JIRA
(v6.2#6252)