Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-3378

[core] Coordinator action's status is SUBMITTED after E1003 error

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: trunk
    • Fix Version/s: trunk, 5.2.0
    • Component/s: core
    • Labels:
      None

      Description

      If I try to run a coordinator job which gives an E1003 error code, the coordinator's status is not changed to FAILED.

      I was using the following coordinator.xml

      <coordinator-app name="cron-coord" frequency="0/10 * * * *" start="${start}" end="${end}" timezone="UTC"
                       xmlns="uri:oozie:coordinator:0.2">
              <action>
              <workflow>
                  <app-path>${workflowAppUri}</app-path>
                  <configuration>
                      <property>
                          <name>resourceManager</name>
                          <value>${resourceManager}</value>
                      </property>
                      <property>
                          <name>nameNode</name>
                          <value>${nameNode}</value>
                      </property>
                      <property>
                          <name>queueName</name>
                          <value>${queueName}</value>
                      </property>
                      <property>
                          <name>user.name</name>
                          <value>admin</value>
                      </property>             
                  </configuration>
              </workflow>
          </action>
      </coordinator-app>
      

      The status of the coordinator job is RUNNING

      $ oozie job -oozie http://localhost:11000/oozie -info 0000000-181105104843399-oozie-andr-C
      Job ID : 0000000-181105104843399-oozie-andr-C
      ------------------------------------------------------------------------------------------------------------------------------------
      Job Name    : cron-coord
      App Path    : hdfs://localhost:9000/user/andrassalamon/examples/apps/cron-schedule
      Status      : RUNNING
      Start Time  : 2010-01-01 00:00 GMT
      End Time    : 2010-01-01 01:00 GMT
      Pause Time  : -
      Concurrency : 1
      ------------------------------------------------------------------------------------------------------------------------------------
      ID                                         Status    Ext ID                               Err Code  Created              Nominal Time         
      0000000-181105104843399-oozie-andr-C@1     SUBMITTED -                                    -         2018-11-05 09:54 GMT 2010-01-01 00:00 GMT 
      ------------------------------------------------------------------------------------------------------------------------------------
      0000000-181105104843399-oozie-andr-C@2     READY     -                                    -         2018-11-05 09:54 GMT 2010-01-01 00:10 GMT 
      ------------------------------------------------------------------------------------------------------------------------------------
      0000000-181105104843399-oozie-andr-C@3     READY     -                                    -         2018-11-05 09:54 GMT 2010-01-01 00:20 GMT 
      ------------------------------------------------------------------------------------------------------------------------------------
      0000000-181105104843399-oozie-andr-C@4     READY     -                                    -         2018-11-05 09:54 GMT 2010-01-01 00:30 GMT 
      ------------------------------------------------------------------------------------------------------------------------------------
      0000000-181105104843399-oozie-andr-C@5     READY     -                                    -         2018-11-05 09:54 GMT 2010-01-01 00:40 GMT 
      ------------------------------------------------------------------------------------------------------------------------------------
      0000000-181105104843399-oozie-andr-C@6     READY     -                                    -         2018-11-05 09:54 GMT 2010-01-01 00:50 GMT 
      ------------------------------------------------------------------------------------------------------------------------------------
      

      The status of the first coordinator action is SUBMITTED

      $ ./distro/target/oozie-5.2.0-SNAPSHOT-distro/oozie-5.2.0-SNAPSHOT/bin/oozie job -oozie http://localhost:11000/oozie -info 0000000-181105104843399-oozie-andr-C@1
      ID : 0000000-181105104843399-oozie-andr-C@1
      ------------------------------------------------------------------------------------------------------------------------------------
      Action Number        : 1
      Console URL          : -
      Error Code           : -
      Error Message        : -
      External ID          : -
      External Status      : -
      Job ID               : 0000000-181105104843399-oozie-andr-C
      Tracker URI          : -
      Created              : 2018-11-05 09:54 GMT
      Nominal Time         : 2010-01-01 00:00 GMT
      Status               : SUBMITTED
      Last Modified        : 2018-11-05 09:54 GMT
      First Missing Dependency : -
      ------------------------------------------------------------------------------------------------------------------------------------
      

      The log contains the E1003 error message:

      $ oozie job -oozie http://localhost:11000/oozie -log 0000000-181105104843399-oozie-andr-C
      ...
      2018-11-05 11:04:57,837 ERROR CoordActionStartXCommand:517 - SERVER[SalamonAndras-MBP15.local] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[0000000-181105104843399-oozie-andr-C] ACTION[0000000-181105104843399-oozie-andr-C@1] XException, 
      org.apache.oozie.command.CommandException: E1003: Invalid coordinator application attributes, user.name=admin
      	at org.apache.oozie.command.coord.CoordActionStartXCommand.mergeConfig(CoordActionStartXCommand.java:180)
      	at org.apache.oozie.command.coord.CoordActionStartXCommand.execute(CoordActionStartXCommand.java:197)
      	at org.apache.oozie.command.coord.CoordActionStartXCommand.execute(CoordActionStartXCommand.java:63)
      	at org.apache.oozie.command.XCommand.call(XCommand.java:291)
      	at org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:363)
      	at org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:292)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:210)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      ...
      

      We should change the status to FAILED in this case.

        Attachments

        1. OOZIE-3378-01.patch
          5 kB
          Andras Salamon
        2. OOZIE-3378-02.patch
          6 kB
          Andras Salamon

          Issue Links

            Activity

              People

              • Assignee:
                asalamon74 Andras Salamon
                Reporter:
                asalamon74 Andras Salamon
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: