[ 
https://issues.apache.org/jira/browse/OOZIE-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367646#comment-15367646
 ] 

abhishek bafna commented on OOZIE-2582:
---------------------------------------

The above three test cases failed because {{externalChildId}} did not get 
populated correctly. The reason I guess is the, way logs are getting generated 
in the launched mapper job is different than what we have set (during the 
tests). This works fine for my local system and for the manual testing also. 
This is the common pattern we are using across most of the actions.

{code}
        Pattern.compile("Submitted application (application[0-9_]*)")
        ......
        
hadoopProps.setProperty("log4j.logger.org.apache.hadoop.yarn.client.api.impl.YarnClientImpl",
 "INFO, jobid");
{code}

Log snippet from failed testcase: (Here jenkins does not provide launcher job 
logs)
{noformat}
11:54:57,562  INFO TestSqoopActionExecutor:520 - USER[test] GROUP[-] TOKEN[] 
APP[testApp] JOB[0000000-160708115326305-oozie-jenk-W] 
ACTION[0000000-160708115326305-oozie-jenk-W@sqoop-action] Waiting up to 
[338,957] msec
11:54:58,564  INFO TestSqoopActionExecutor:520 - USER[test] GROUP[-] TOKEN[] 
APP[testApp] JOB[0000000-160708115326305-oozie-jenk-W] 
ACTION[0000000-160708115326305-oozie-jenk-W@sqoop-action] Waiting up to 
[337,954] msec
11:54:59,590  INFO SqoopActionExecutor:520 - USER[test] GROUP[-] TOKEN[] 
APP[testApp] JOB[0000000-160708115401290-oozie-jenk-W] 
ACTION[0000000-160708115401290-oozie-jenk-W@sqoop-action] Hadoop Jobs launched 
: []
11:54:59,591  INFO SqoopActionExecutor:520 - USER[test] GROUP[-] TOKEN[] 
APP[testApp] JOB[0000000-160708115401290-oozie-jenk-W] 
ACTION[0000000-160708115401290-oozie-jenk-W@sqoop-action] action completed, 
external ID [job_20160708115311064_0002]
11:54:59,595  INFO SqoopActionExecutor:520 - USER[test] GROUP[-] TOKEN[] 
APP[testApp] JOB[0000000-160708115401290-oozie-jenk-W] 
ACTION[0000000-160708115401290-oozie-jenk-W@sqoop-action] action produced output
11:54:59,606  WARN SqoopActionExecutor:523 - USER[test] GROUP[-] TOKEN[] 
APP[testApp] JOB[0000000-160708115401290-oozie-jenk-W] 
ACTION[0000000-160708115401290-oozie-jenk-W@sqoop-action] Can't find any 
associated Hadoop job counters
{noformat}

Log snippet from locally executed testcase:
{noformat}
18:23:41,801  INFO clienttrace:738 - src: /127.0.0.1:51440, dest: 
/127.0.0.1:51853, bytes: 282, op: HDFS_READ, cliID: 
DFSClient_NONMAPREDUCE_-1910360185_1, offset: 0, srvID: 
2a57c80d-2d22-44a3-aedd-6f26eb7be1ee, blockid: 
BP-1921712297-192.168.0.4-1467982356696:blk_1073741976_1152, duration: 102000
18:23:41,802  INFO SqoopActionExecutor:520 - USER[test] GROUP[-] TOKEN[] 
APP[testApp] JOB[0000000-160708182307631-oozie-abaf-W] 
ACTION[0000000-160708182307631-oozie-abaf-W@sqoop-action] Hadoop Jobs launched 
: [job_1467982372341_0002]
18:23:41,803  INFO SqoopActionExecutor:520 - USER[test] GROUP[-] TOKEN[] 
APP[testApp] JOB[0000000-160708182307631-oozie-abaf-W] 
ACTION[0000000-160708182307631-oozie-abaf-W@sqoop-action] action completed, 
external ID [job_1467982372341_0001]
18:23:41,851  INFO SqoopActionExecutor:520 - USER[test] GROUP[-] TOKEN[] 
APP[testApp] JOB[0000000-160708182307631-oozie-abaf-W] 
ACTION[0000000-160708182307631-oozie-abaf-W@sqoop-action] action produced output
18:23:41,854  INFO audit:7743 - allowed=true    ugi=test (auth:PROXY) via 
abafna (auth:SIMPLE)  ip=/127.0.0.1   cmd=getfileinfo 
src=/user/test/oozie-abaf/0000000-160708182307631-oozie-abaf-W/sqoop-action--sqoop
      dst=null        perm=null
{noformat}


> Populating external child Ids for action failures
> -------------------------------------------------
>
>                 Key: OOZIE-2582
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2582
>             Project: Oozie
>          Issue Type: Bug
>          Components: core
>            Reporter: abhishek bafna
>            Assignee: abhishek bafna
>         Attachments: OOZIE-2582-00.patch, OOZIE-2582-01.patch, 
> OOZIE-2582-02.patch, OOZIE-2582-03.patch
>
>
> Currently Oozie external child ids are populated into workflow bean, when the 
> job/action completes successfully. It should populate external child ids in 
> case of job failures as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to