Oozie
  1. Oozie
  2. OOZIE-739

a coord action fails because the uri points to a namenode that is not in whitelist. the E0901 error shows in the oozie.log, but not written to the database

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: trunk
    • Fix Version/s: 3.3.2
    • Component/s: coordinator
    • Labels:
      None

      Description

      a coord action fails because the uri points to a namenode that is not in
      whitelist. the E0901 error shows in the oozie.log. but the error code and error
      message does not display in oozie job -info action# -verbose. for example,

      $ oozie job -log 0000028-100625200833755-oozie-oozi-C
      ...
      2010-06-28 18:50:56,502 DEBUG CoordActionInputCheckCommand:544 - USER[mchiang]
      GROUP[users] TOKEN[] APP[coord-21-20] JOB[0000028-100625200833755-oozie-oozi-C]
      ACTION[-] checking for the file
      2010-06-28 18:50:56,502 WARN CoordActionInputCheckCommand:541 - USER[mchiang]
      GROUP[users] TOKEN[] APP[coord-21-20] JOB[0000028-100625200833755-oozie-oozi-C]
      ACTION[-] 0000028-100625200833755-oozie-oozi-C@1: Exception occurs:
      java.io.IOException: org.apache.oozie.service.HadoopAccessorException: E0901:
      Namenode [XXXXX:8020] not allowed, not in Oozies
      whitelist STORE is active true
      java.io.IOException: org.apache.oozie.service.HadoopAccessorException: E0901:
      Namenode [XXXXX:8020] not allowed, not in Oozies
      whitelist
      ...

      $ oozie job -info 0000028-100625200833755-oozie-oozi-C@1 -verbose
      ID : 0000028-100625200833755-oozie-oozi-C@1
      ------------------------------------------------------------------------------------------------------------------------------------
      Action Number : 1
      Console URL : -
      Error Code : -
      Error Message : -
      External ID : -
      External Status : -
      Job ID : 0000028-100625200833755-oozie-oozi-C
      Tracker URI : -
      Created : 2010-06-28 18:50
      Status : WAITING
      Last Modified : 2010-06-28 18:50
      Missing Dependencies :
      hdfs://XXXXX/_SUCCESS
      ------------------------------------------------------------------------------------------------------------------------------------

        Activity

        Rohini Palaniswamy made changes -
        Fix Version/s trunk [ 12323240 ]
        Robert Kanter made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Robert Kanter made changes -
        Fix Version/s 3.3.2 [ 12323993 ]
        Virag Kothari made changes -
        Status Patch Available [ 10002 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Mona Chitnis made changes -
        Attachment OOZIE-739v2.patch [ 12544864 ]
        Mona Chitnis made changes -
        Status Open [ 1 ] Patch Available [ 10002 ]
        Affects Version/s trunk [ 12323240 ]
        Affects Version/s 3.2.0 [ 12320149 ]
        Fix Version/s trunk [ 12323240 ]
        Mona Chitnis made changes -
        Assignee Mohamed Battisha [ mbattish@yahoo.com ] Mona Chitnis [ chitnis ]
        Alejandro Abdelnur made changes -
        Fix Version/s 3.2.0 [ 12320149 ]
        Mohamed Battisha made changes -
        Assignee Mohamed Battisha [ mbattish@yahoo.com ]
        Description a coord action fails because the uri points to a namenode that is not in
        whitelist. the E0901 error shows in the oozie.log. but the error code and error
        message does not display in oozie job -info action# -verbose. for example,

        $ oozie job -log 0000028-100625200833755-oozie-oozi-C
        ...
        2010-06-28 18:50:56,502 DEBUG CoordActionInputCheckCommand:544 - USER[mchiang]
        GROUP[users] TOKEN[] APP[coord-21-20] JOB[0000028-100625200833755-oozie-oozi-C]
        ACTION[-] checking for the file
        hdfs://axoniteblue-nn1.blue.ygrid.yahoo.com:8020/user/mchiang/coord-input/2010/06/11/01/00/_SUCCESS
        2010-06-28 18:50:56,502 WARN CoordActionInputCheckCommand:541 - USER[mchiang]
        GROUP[users] TOKEN[] APP[coord-21-20] JOB[0000028-100625200833755-oozie-oozi-C]
        ACTION[-] 0000028-100625200833755-oozie-oozi-C@1: Exception occurs:
        java.io.IOException: org.apache.oozie.service.HadoopAccessorException: E0901:
        Namenode [axoniteblue-nn1.blue.ygrid.yahoo.com:8020] not allowed, not in Oozies
        whitelist STORE is active true
        java.io.IOException: org.apache.oozie.service.HadoopAccessorException: E0901:
        Namenode [axoniteblue-nn1.blue.ygrid.yahoo.com:8020] not allowed, not in Oozies
        whitelist
        ...


        $ oozie job -info 0000028-100625200833755-oozie-oozi-C@1 -verbose
        ID : 0000028-100625200833755-oozie-oozi-C@1
        ------------------------------------------------------------------------------------------------------------------------------------
        Action Number : 1
        Console URL : -
        Error Code : -
        Error Message : -
        External ID : -
        External Status : -
        Job ID : 0000028-100625200833755-oozie-oozi-C
        Tracker URI : -
        Created : 2010-06-28 18:50
        Status : WAITING
        Last Modified : 2010-06-28 18:50
        Missing Dependencies :
        hdfs://axoniteblue-nn1.blue.ygrid.yahoo.com:8020/user/mchiang/coord-input/2010/06/11/01/00/_SUCCESS
        ------------------------------------------------------------------------------------------------------------------------------------
        a coord action fails because the uri points to a namenode that is not in
        whitelist. the E0901 error shows in the oozie.log. but the error code and error
        message does not display in oozie job -info action# -verbose. for example,

        $ oozie job -log 0000028-100625200833755-oozie-oozi-C
        ...
        2010-06-28 18:50:56,502 DEBUG CoordActionInputCheckCommand:544 - USER[mchiang]
        GROUP[users] TOKEN[] APP[coord-21-20] JOB[0000028-100625200833755-oozie-oozi-C]
        ACTION[-] checking for the file
        2010-06-28 18:50:56,502 WARN CoordActionInputCheckCommand:541 - USER[mchiang]
        GROUP[users] TOKEN[] APP[coord-21-20] JOB[0000028-100625200833755-oozie-oozi-C]
        ACTION[-] 0000028-100625200833755-oozie-oozi-C@1: Exception occurs:
        java.io.IOException: org.apache.oozie.service.HadoopAccessorException: E0901:
        Namenode [XXXXX:8020] not allowed, not in Oozies
        whitelist STORE is active true
        java.io.IOException: org.apache.oozie.service.HadoopAccessorException: E0901:
        Namenode [XXXXX:8020] not allowed, not in Oozies
        whitelist
        ...


        $ oozie job -info 0000028-100625200833755-oozie-oozi-C@1 -verbose
        ID : 0000028-100625200833755-oozie-oozi-C@1
        ------------------------------------------------------------------------------------------------------------------------------------
        Action Number : 1
        Console URL : -
        Error Code : -
        Error Message : -
        External ID : -
        External Status : -
        Job ID : 0000028-100625200833755-oozie-oozi-C
        Tracker URI : -
        Created : 2010-06-28 18:50
        Status : WAITING
        Last Modified : 2010-06-28 18:50
        Missing Dependencies :
        hdfs://XXXXX/_SUCCESS
        ------------------------------------------------------------------------------------------------------------------------------------
        Mohamed Battisha made changes -
        Field Original Value New Value
        Summary a coord action fails because the uri points to a namenode that is not in whitelist. the E0901 error shows in the oozie.log, but not in written to the database a coord action fails because the uri points to a namenode that is not in whitelist. the E0901 error shows in the oozie.log, but not written to the database
        Mohamed Battisha created issue -

          People

          • Assignee:
            Mona Chitnis
            Reporter:
            Mohamed Battisha
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 2h
              2h
              Remaining:
              Remaining Estimate - 2h
              2h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development