Review Board 1.7.22


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

Review Request #4204 - Created March 6, 2012 and updated

Mohamed Battisha
trunk
OOZIE-739
Reviewers
oozie
oozie
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 [XXXXXX: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://XXXXXX:8020/user/mchiang/coord-input/2010/06/11/01/00/_SUCCESS 
------------------------------------------------------------------------------------------------------------------------------------ 

 
Review request changed
Updated (March 23, 2012, 4:34 p.m.)
Adding unit test codes and addressing review feedback
Posted (March 26, 2012, 8:52 p.m.)
Few comments.
Move to the previous line as per Java coding convention
Can you add a note on why the CommandException is being thrown?
Will be good to add descriptive error message in addition to chaining the exception.
The formatting is off for the comments and the method by a couple of tabs.
Can you add a note on strings that are discarded?
The formatting is off for the comments and the method by a couple of tabs.
Resetting (not resting)
The formatting is off for the by a tab.
If no exception is thrown then the test case will pass. In order to catch this, add a fail() immediately after the call to pathExists
Posted (June 18, 2012, 10:38 p.m.)
any update on this JIRA?
  1. I'll take this up. Thanks for the scrub tucu.