Skip to search.

Breaking News Visit Yahoo! News for the latest.

×Close this window

Oozie-users · Please go to Apache Incubator Oozie

The Yahoo! Groups Product Blog

Check it out!

Group Information

  • Members: 191
  • Category: Open Source
  • Founded: Jun 24, 2010
  • Language: English
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Real people. Real stories. See how Yahoo! Groups impacts members worldwide.

Messages

Advanced
Messages Help
Messages 2022 - 2051 of 2051   Oldest  |  < Older  |  Newer >  |  Newest
Messages: Show Message Summaries Sort by Date ^  
#2022 From: "Felix" <felixgao@...>
Date: Wed Aug 24, 2011 4:53 pm
Subject: Re: Oozie error when submitting jobs
felixgao
Send Email Send Email
 
NN is running on a different box and so is JT. I do have access to NN and JT
from localhost, the box that is used for oozie used to be the launchpad for all
of our pig jobs.  When I do hadoop fs I will be able to view the HDFS for which
ever user that I am logged in with.

For my test pig I only have the following in the HDFS
hadoop fs -ls /user/felix/oozie/workflows/test_pig
Found 2 items
-rw-r--r--   2 felix supergroup        367 2011-08-23 14:28
/user/felix/oozie/workflows/test_pig/config-default.xml
drwxr-xr-x   - felix supergroup          0 2011-08-23 14:08
/user/felix/oozie/workflows/test_pig/lib


The lib is empty right now.
In my local directory I have
ls -al
total 28
drwxrwxr-x 2 felix felix 4096 Aug 23 16:14 .
drwxrwxr-x 3 felix felix 4096 Aug 23 13:07 ..
-rw-rw-r-- 1 felix felix  367 Aug 23 14:28 config-default.xml
-rw-rw-r-- 1 felix felix  486 Aug 23 15:56 job.properties
-rw-rw-r-- 1 felix felix  309 Aug 23 15:02 pigexample.pig
-rw-rw-r-- 1 felix felix 1190 Aug 23 15:41 pig-wf.xml
-rwxrwxrwx 1 felix felix  929 Aug 23 16:09 submit.sh

  cat job.properties
#The following attributes must be set
fs.default.name=hdfs://namenode.xxx.xxx:50001
mapred.job.tracker=jobtracker.xxx.xxx:50002
oozie.use.system.libpath=true
oozie.libpath=hdfs://namenode.xxx.xxx:50001/user/oozie/share/pig/lib/
queueName=default
#additional
oozie.wf.application.path=hdfs://namenode.xxx.xxx:50001/user/felix/oozie/workflo\
ws/test_pig
inputDir=/user/felix/test_input.data
outputDir=/user/felix/oozie_output/pig_test

I submitted the job to Oozie using
oozie pig -oozie http://localhost:11000/oozie -file pigexample.pig -config
job.properties

hadoop we are using is 0.20.2 and oozie we are using is 2.3.0. Both are from
cloudera's RPM.

I hope this is clear enough.

--- In Oozie-users@yahoogroups.com, Mohammad Islam <mislam77@...> wrote:
>
> Do you have the NN running on the same box?
>
> If not,  do you have the access from the localhost to NN? Did you able to run
"haddop fs ..." command from the localhost?
>
>
> Which version of hadoop and what version of oozie you are using?
> What is the wf apppath in job.properties?
>
> Regards,
> Mohammad
>
>
>
>
> ________________________________
> From: Felix <felixgao@...>
> To: Oozie-users@yahoogroups.com
> Sent: Tuesday, August 23, 2011 3:28 PM
> Subject: [Oozie-users] Oozie error when submitting jobs
>
>
>  
> Hi all I have a simple pig job for testing that I would like to use oozie to
manage.  When I do the following I got
>
> oozie pig -oozie http://localhost:11000/oozie -file pigexample.pig -config
job.properties
> Error: E0902 : E0902: Exception occured: [java.io.IOException: Call to
namenode/69.xxx.xxx.xxx:50001 failed on local exception: java.io.EOFException]
>
> 2011-08-23 17:18:11,861  WARN V1JobsServlet:528 - USER[felix] GROUP[users]
TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
http://localhost:11000/oozie/v1/jobs?jobtype=pig] error[E0902], E0902: Exception
occured: [java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed on
local exception: java.io.EOFException]
> org.apache.oozie.servlet.XServletException: E0902: Exception occured:
[java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed on local
exception: java.io.EOFException]
> at
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:179)
> at org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:290)
> at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> at
com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.j\
ava:371)
> at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:235)
> at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2\
33)
> at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1\
91)
> at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109\
)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Pr\
otocol.java:588)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: org.apache.oozie.service.AuthorizationException: E0902: Exception
occured: [java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed on
local exception: java.io.EOFException]
> at
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:318)
> at
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:171)
> ... 21 more
> Caused by: org.apache.oozie.service.HadoopAccessorException: E0902: Exception
occured: [java.io.IOException: Call to
namenode.chi.bluekai.com/69.170.130.176:50001 failed on local exception:
java.io.EOFException]
> at
org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorSe\
rvice.java:144)
> at
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:283)
> ... 22 more
> Caused by: java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed
on local exception: java.io.EOFException
> at org.apache.hadoop.ipc.Client.wrapException(Client.java:1142)
> at org.apache.hadoop.ipc.Client.call(Client.java:1110)
> at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:226)
> at $Proxy22.getProtocolVersion(Unknown Source)
> at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:398)
> at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:384)
> at org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:111)
> at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:213)
> at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:180)
> at
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.ja\
va:89)
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1514)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:67)
> at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:1548)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1530)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:228)
> at
org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorSe\
rvice.java:141)
> ... 23 more
> Caused by: java.io.EOFException
> at java.io.DataInputStream.readInt(DataInputStream.java:375)
> at org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:815)
> at org.apache.hadoop.ipc.Client$Connection.run(Client.java:724)
>
> in my oozie-site.xml I have the following services
> <property>
> <name>oozie.services</name>
> <value>
> org.apache.oozie.service.SchedulerService,
> org.apache.oozie.service.InstrumentationService,
> org.apache.oozie.service.CallableQueueService,
> org.apache.oozie.service.UUIDService,
> org.apache.oozie.service.ELService,
> org.apache.oozie.service.AuthorizationService,
> org.apache.oozie.service.MemoryLocksService,
> org.apache.oozie.service.DagXLogInfoService,
> org.apache.oozie.service.SchemaService,
> org.apache.oozie.service.LiteWorkflowAppService,
> org.apache.oozie.service.StoreService,
> org.apache.oozie.service.CoordinatorStoreService,
> org.apache.oozie.service.SLAStoreService,
> org.apache.oozie.service.DBLiteWorkflowStoreService,
> org.apache.oozie.service.CallbackService,
> org.apache.oozie.service.ActionService,
> org.apache.oozie.service.ActionCheckerService,
> org.apache.oozie.service.RecoveryService,
> org.apache.oozie.service.PurgeService,
> org.apache.oozie.service.CoordinatorEngineService,
> org.apache.oozie.service.DagEngineService,
> org.apache.oozie.service.CoordJobMatLookupTriggerService,
> org.apache.oozie.service.HadoopAccessorService
> </value>
> <description>
> All services to be created and managed by Oozie Services singleton.
> Class names must be separated by commas.
> </description>
> </property>
>
> if I take out org.apache.oozie.service.HadoopAccessorService, then I will get
> 2011-08-23 16:09:45,587 ERROR V1JobsServlet:522 - USER[felix] GROUP[users]
TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
http://localhost:11000/oozie/v1/jobs?jobtype=pig] error, null
> java.lang.NullPointerException
> at
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:283)
> at
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:171)
> at org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:290)
> at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> at
com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.j\
ava:371)
> at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:235)
> at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2\
33)
> at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1\
91)
> at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109\
)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Pr\
otocol.java:588)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> at java.lang.Thread.run(Thread.java:619)
>
> your help is appreciated.
>
> Felix
>

#2023 From: Alejandro Abdelnur <tucu@...>
Date: Wed Aug 24, 2011 4:58 pm
Subject: Re: Re: Oozie error when submitting jobs
tucu0
Send Email Send Email
 
Felix,

What are doing that you need to modify the service classes?

Thanks.

Alejandro

On Wed, Aug 24, 2011 at 9:53 AM, Felix <felixgao@...> wrote:
NN is running on a different box and so is JT. I do have access to NN and JT from localhost, the box that is used for oozie used to be the launchpad for all of our pig jobs.  When I do hadoop fs I will be able to view the HDFS for which ever user that I am logged in with.

For my test pig I only have the following in the HDFS
hadoop fs -ls /user/felix/oozie/workflows/test_pig
Found 2 items
-rw-r--r--   2 felix supergroup        367 2011-08-23 14:28 /user/felix/oozie/workflows/test_pig/config-default.xml
drwxr-xr-x   - felix supergroup          0 2011-08-23 14:08 /user/felix/oozie/workflows/test_pig/lib


The lib is empty right now.
In my local directory I have
ls -al
total 28
drwxrwxr-x 2 felix felix 4096 Aug 23 16:14 .
drwxrwxr-x 3 felix felix 4096 Aug 23 13:07 ..
-rw-rw-r-- 1 felix felix  367 Aug 23 14:28 config-default.xml
-rw-rw-r-- 1 felix felix  486 Aug 23 15:56 job.properties
-rw-rw-r-- 1 felix felix  309 Aug 23 15:02 pigexample.pig
-rw-rw-r-- 1 felix felix 1190 Aug 23 15:41 pig-wf.xml
-rwxrwxrwx 1 felix felix  929 Aug 23 16:09 submit.sh

 cat job.properties
#The following attributes must be set
fs.default.name=hdfs://namenode.xxx.xxx:50001
mapred.job.tracker=jobtracker.xxx.xxx:50002
oozie.use.system.libpath=true
oozie.libpath=hdfs://namenode.xxx.xxx:50001/user/oozie/share/pig/lib/
queueName=default
#additional
oozie.wf.application.path=hdfs://namenode.xxx.xxx:50001/user/felix/oozie/workflows/test_pig
inputDir=/user/felix/test_input.data
outputDir=/user/felix/oozie_output/pig_test

I submitted the job to Oozie using
oozie pig -oozie http://localhost:11000/oozie -file pigexample.pig -config job.properties

hadoop we are using is 0.20.2 and oozie we are using is 2.3.0. Both are from cloudera's RPM.

I hope this is clear enough.

--- In Oozie-users@yahoogroups.com, Mohammad Islam <mislam77@...> wrote:
>
> Do you have the NN running on the same box?
>
> If not,  do you have the access from the localhost to NN? Did you able to run "haddop fs ..." command from the localhost?
>
>
> Which version of hadoop and what version of oozie you are using?
> What is the wf apppath in job.properties?
>
> Regards,
> Mohammad
>
>
>
>
> ________________________________
> From: Felix <felixgao@...>
> To: Oozie-users@yahoogroups.com
> Sent: Tuesday, August 23, 2011 3:28 PM
> Subject: [Oozie-users] Oozie error when submitting jobs
>
>
>  
> Hi all I have a simple pig job for testing that I would like to use oozie to manage.  When I do the following I got
>
> oozie pig -oozie http://localhost:11000/oozie -file pigexample.pig -config job.properties
> Error: E0902 : E0902: Exception occured: [java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed on local exception: java.io.EOFException]
>
> 2011-08-23 17:18:11,861  WARN V1JobsServlet:528 - USER[felix] GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST http://localhost:11000/oozie/v1/jobs?jobtype=pig] error[E0902], E0902: Exception occured: [java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed on local exception: java.io.EOFException]
> org.apache.oozie.servlet.XServletException: E0902: Exception occured: [java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed on local exception: java.io.EOFException]
> at org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:179)
> at org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> at com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:371)
> at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: org.apache.oozie.service.AuthorizationException: E0902: Exception occured: [java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed on local exception: java.io.EOFException]
> at org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:318)
> at org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:171)
> ... 21 more
> Caused by: org.apache.oozie.service.HadoopAccessorException: E0902: Exception occured: [java.io.IOException: Call to namenode.chi.bluekai.com/69.170.130.176:50001 failed on local exception: java.io.EOFException]
> at org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorService.java:144)
> at org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:283)
> ... 22 more
> Caused by: java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed on local exception: java.io.EOFException
> at org.apache.hadoop.ipc.Client.wrapException(Client.java:1142)
> at org.apache.hadoop.ipc.Client.call(Client.java:1110)
> at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:226)
> at $Proxy22.getProtocolVersion(Unknown Source)
> at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:398)
> at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:384)
> at org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:111)
> at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:213)
> at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:180)
> at org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:89)
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1514)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:67)
> at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:1548)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1530)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:228)
> at org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorService.java:141)
> ... 23 more
> Caused by: java.io.EOFException
> at java.io.DataInputStream.readInt(DataInputStream.java:375)
> at org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:815)
> at org.apache.hadoop.ipc.Client$Connection.run(Client.java:724)
>
> in my oozie-site.xml I have the following services
> <property>
> <name>oozie.services</name>
> <value>
> org.apache.oozie.service.SchedulerService,
> org.apache.oozie.service.InstrumentationService,
> org.apache.oozie.service.CallableQueueService,
> org.apache.oozie.service.UUIDService,
> org.apache.oozie.service.ELService,
> org.apache.oozie.service.AuthorizationService,
> org.apache.oozie.service.MemoryLocksService,
> org.apache.oozie.service.DagXLogInfoService,
> org.apache.oozie.service.SchemaService,
> org.apache.oozie.service.LiteWorkflowAppService,
> org.apache.oozie.service.StoreService,
> org.apache.oozie.service.CoordinatorStoreService,
> org.apache.oozie.service.SLAStoreService,
> org.apache.oozie.service.DBLiteWorkflowStoreService,
> org.apache.oozie.service.CallbackService,
> org.apache.oozie.service.ActionService,
> org.apache.oozie.service.ActionCheckerService,
> org.apache.oozie.service.RecoveryService,
> org.apache.oozie.service.PurgeService,
> org.apache.oozie.service.CoordinatorEngineService,
> org.apache.oozie.service.DagEngineService,
> org.apache.oozie.service.CoordJobMatLookupTriggerService,
> org.apache.oozie.service.HadoopAccessorService
> </value>
> <description>
> All services to be created and managed by Oozie Services singleton.
> Class names must be separated by commas.
> </description>
> </property>
>
> if I take out org.apache.oozie.service.HadoopAccessorService, then I will get
> 2011-08-23 16:09:45,587 ERROR V1JobsServlet:522 - USER[felix] GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST http://localhost:11000/oozie/v1/jobs?jobtype=pig] error, null
> java.lang.NullPointerException
> at org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:283)
> at org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:171)
> at org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> at com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:371)
> at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> at java.lang.Thread.run(Thread.java:619)
>
> your help is appreciated.
>
> Felix
>




------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
   http://groups.yahoo.com/group/Oozie-users/

<*> Your email settings:
   Individual Email | Traditional

<*> To change settings online go to:
   http://groups.yahoo.com/group/Oozie-users/join
   (Yahoo! ID required)

<*> To change settings via email:
   Oozie-users-digest@yahoogroups.com
   Oozie-users-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
   Oozie-users-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
   http://docs.yahoo.com/info/terms/



#2024 From: "Felix" <felixgao@...>
Date: Wed Aug 24, 2011 6:15 pm
Subject: Re: Oozie error when submitting jobs
felixgao
Send Email Send Email
 
Alejandro,

I am modifying the oozie.services to
<property>
         <name>oozie.services</name>
         <value>
             org.apache.oozie.service.SchedulerService,
             org.apache.oozie.service.InstrumentationService,
             org.apache.oozie.service.CallableQueueService,
             org.apache.oozie.service.UUIDService,
             org.apache.oozie.service.ELService,
             org.apache.oozie.service.AuthorizationService,
             org.apache.oozie.service.MemoryLocksService,
             org.apache.oozie.service.DagXLogInfoService,
             org.apache.oozie.service.SchemaService,
             org.apache.oozie.service.LiteWorkflowAppService,
             org.apache.oozie.service.StoreService,
             org.apache.oozie.service.CoordinatorStoreService,
             org.apache.oozie.service.SLAStoreService,
             org.apache.oozie.service.DBLiteWorkflowStoreService,
             org.apache.oozie.service.CallbackService,
             org.apache.oozie.service.ActionService,
             org.apache.oozie.service.ActionCheckerService,
             org.apache.oozie.service.RecoveryService,
             org.apache.oozie.service.PurgeService,
             org.apache.oozie.service.CoordinatorEngineService,
             org.apache.oozie.service.DagEngineService,
             org.apache.oozie.service.CoordJobMatLookupTriggerService,
             org.apache.oozie.service.HadoopAccessorService
         </value>
         <description>
             All services to be created and managed by Oozie Services singleton.
             Class names must be separated by commas.
         </description>
     </property>

because I am seeing E0902: Exception occured:  so
https://github.com/yahoo/oozie/wiki/FAQ told me to add those to the xml file.

--- In Oozie-users@yahoogroups.com, Alejandro Abdelnur <tucu@...> wrote:
>
> Felix,
>
> What are doing that you need to modify the service classes?
>
> Thanks.
>
> Alejandro
>
> On Wed, Aug 24, 2011 at 9:53 AM, Felix <felixgao@...> wrote:
>
> > NN is running on a different box and so is JT. I do have access to NN and
> > JT from localhost, the box that is used for oozie used to be the launchpad
> > for all of our pig jobs.  When I do hadoop fs I will be able to view the
> > HDFS for which ever user that I am logged in with.
> >
> > For my test pig I only have the following in the HDFS
> > hadoop fs -ls /user/felix/oozie/workflows/test_pig
> > Found 2 items
> > -rw-r--r--   2 felix supergroup        367 2011-08-23 14:28
> > /user/felix/oozie/workflows/test_pig/config-default.xml
> > drwxr-xr-x   - felix supergroup          0 2011-08-23 14:08
> > /user/felix/oozie/workflows/test_pig/lib
> >
> >
> > The lib is empty right now.
> > In my local directory I have
> > ls -al
> > total 28
> > drwxrwxr-x 2 felix felix 4096 Aug 23 16:14 .
> > drwxrwxr-x 3 felix felix 4096 Aug 23 13:07 ..
> > -rw-rw-r-- 1 felix felix  367 Aug 23 14:28 config-default.xml
> > -rw-rw-r-- 1 felix felix  486 Aug 23 15:56 job.properties
> > -rw-rw-r-- 1 felix felix  309 Aug 23 15:02 pigexample.pig
> > -rw-rw-r-- 1 felix felix 1190 Aug 23 15:41 pig-wf.xml
> > -rwxrwxrwx 1 felix felix  929 Aug 23 16:09 submit.sh
> >
> >  cat job.properties
> > #The following attributes must be set
> > fs.default.name=hdfs://namenode.xxx.xxx:50001
> > mapred.job.tracker=jobtracker.xxx.xxx:50002
> > oozie.use.system.libpath=true
> > oozie.libpath=hdfs://namenode.xxx.xxx:50001/user/oozie/share/pig/lib/
> > queueName=default
> > #additional
> >
> >
oozie.wf.application.path=hdfs://namenode.xxx.xxx:50001/user/felix/oozie/workflo\
ws/test_pig
> > inputDir=/user/felix/test_input.data
> > outputDir=/user/felix/oozie_output/pig_test
> >
> > I submitted the job to Oozie using
> > oozie pig -oozie http://localhost:11000/oozie -file pigexample.pig -config
> > job.properties
> >
> > hadoop we are using is 0.20.2 and oozie we are using is 2.3.0. Both are
> > from cloudera's RPM.
> >
> > I hope this is clear enough.
> >
> > --- In Oozie-users@yahoogroups.com, Mohammad Islam <mislam77@> wrote:
> > >
> > > Do you have the NN running on the same box?
> > >
> > > If not,  do you have the access from the localhost to NN? Did you able
> > to run "haddop fs ..." command from the localhost?
> > >
> > >
> > > Which version of hadoop and what version of oozie you are using?
> > > What is the wf apppath in job.properties?
> > >
> > > Regards,
> > > Mohammad
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: Felix <felixgao@>
> > > To: Oozie-users@yahoogroups.com
> > > Sent: Tuesday, August 23, 2011 3:28 PM
> > > Subject: [Oozie-users] Oozie error when submitting jobs
> > >
> > >
> > > Â
> > > Hi all I have a simple pig job for testing that I would like to use oozie
> > to manage.  When I do the following I got
> > >
> > > oozie pig -oozie http://localhost:11000/oozie -file pigexample.pig
> > -config job.properties
> > > Error: E0902 : E0902: Exception occured: [java.io.IOException: Call to
> > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > java.io.EOFException]
> > >
> > > 2011-08-23 17:18:11,861  WARN V1JobsServlet:528 - USER[felix]
> > GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
> > http://localhost:11000/oozie/v1/jobs?jobtype=pig] error[E0902], E0902:
> > Exception occured: [java.io.IOException: Call to
> > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > java.io.EOFException]
> > > org.apache.oozie.servlet.XServletException: E0902: Exception occured:
> > [java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed on local
> > exception: java.io.EOFException]
> > > at
> >
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:179)
> > > at
> > org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> > > at
> > org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> > > at
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:290)
> > > at
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> > > at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> > > at
> >
com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.j\
ava:371)
> > > at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> > > at
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:235)
> > > at
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> > > at
> >
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2\
33)
> > > at
> >
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1\
91)
> > > at
> >
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> > > at
> >
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> > > at
> >
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109\
)
> > > at
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> > > at
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> > > at
> >
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Pr\
otocol.java:588)
> > > at
> > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> > > at java.lang.Thread.run(Thread.java:619)
> > > Caused by: org.apache.oozie.service.AuthorizationException: E0902:
> > Exception occured: [java.io.IOException: Call to
> > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > java.io.EOFException]
> > > at
> >
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:318)
> > > at
> >
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:171)
> > > ... 21 more
> > > Caused by: org.apache.oozie.service.HadoopAccessorException: E0902:
> > Exception occured: [java.io.IOException: Call to
> > namenode.chi.bluekai.com/69.170.130.176:50001 failed on local exception:
> > java.io.EOFException]
> > > at
> >
org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorSe\
rvice.java:144)
> > > at
> >
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:283)
> > > ... 22 more
> > > Caused by: java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001
> > failed on local exception: java.io.EOFException
> > > at org.apache.hadoop.ipc.Client.wrapException(Client.java:1142)
> > > at org.apache.hadoop.ipc.Client.call(Client.java:1110)
> > > at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:226)
> > > at $Proxy22.getProtocolVersion(Unknown Source)
> > > at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:398)
> > > at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:384)
> > > at org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:111)
> > > at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:213)
> > > at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:180)
> > > at
> >
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.ja\
va:89)
> > > at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1514)
> > > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:67)
> > > at
> > org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:1548)
> > > at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1530)
> > > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:228)
> > > at
> >
org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorSe\
rvice.java:141)
> > > ... 23 more
> > > Caused by: java.io.EOFException
> > > at java.io.DataInputStream.readInt(DataInputStream.java:375)
> > > at
> > org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:815)
> > > at org.apache.hadoop.ipc.Client$Connection.run(Client.java:724)
> > >
> > > in my oozie-site.xml I have the following services
> > > <property>
> > > <name>oozie.services</name>
> > > <value>
> > > org.apache.oozie.service.SchedulerService,
> > > org.apache.oozie.service.InstrumentationService,
> > > org.apache.oozie.service.CallableQueueService,
> > > org.apache.oozie.service.UUIDService,
> > > org.apache.oozie.service.ELService,
> > > org.apache.oozie.service.AuthorizationService,
> > > org.apache.oozie.service.MemoryLocksService,
> > > org.apache.oozie.service.DagXLogInfoService,
> > > org.apache.oozie.service.SchemaService,
> > > org.apache.oozie.service.LiteWorkflowAppService,
> > > org.apache.oozie.service.StoreService,
> > > org.apache.oozie.service.CoordinatorStoreService,
> > > org.apache.oozie.service.SLAStoreService,
> > > org.apache.oozie.service.DBLiteWorkflowStoreService,
> > > org.apache.oozie.service.CallbackService,
> > > org.apache.oozie.service.ActionService,
> > > org.apache.oozie.service.ActionCheckerService,
> > > org.apache.oozie.service.RecoveryService,
> > > org.apache.oozie.service.PurgeService,
> > > org.apache.oozie.service.CoordinatorEngineService,
> > > org.apache.oozie.service.DagEngineService,
> > > org.apache.oozie.service.CoordJobMatLookupTriggerService,
> > > org.apache.oozie.service.HadoopAccessorService
> > > </value>
> > > <description>
> > > All services to be created and managed by Oozie Services singleton.
> > > Class names must be separated by commas.
> > > </description>
> > > </property>
> > >
> > > if I take out org.apache.oozie.service.HadoopAccessorService, then I will
> > get
> > > 2011-08-23 16:09:45,587 ERROR V1JobsServlet:522 - USER[felix]
> > GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
> > http://localhost:11000/oozie/v1/jobs?jobtype=pig] error, null
> > > java.lang.NullPointerException
> > > at
> >
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:283)
> > > at
> >
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:171)
> > > at
> > org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> > > at
> > org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> > > at
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:290)
> > > at
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> > > at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> > > at
> >
com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.j\
ava:371)
> > > at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> > > at
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:235)
> > > at
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> > > at
> >
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2\
33)
> > > at
> >
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1\
91)
> > > at
> >
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> > > at
> >
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> > > at
> >
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109\
)
> > > at
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> > > at
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> > > at
> >
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Pr\
otocol.java:588)
> > > at
> > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> > > at java.lang.Thread.run(Thread.java:619)
> > >
> > > your help is appreciated.
> > >
> > > Felix
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>

#2025 From: Alejandro Abdelnur <tucu@...>
Date: Wed Aug 24, 2011 6:30 pm
Subject: Re: Re: Oozie error when submitting jobs
tucu0
Send Email Send Email
 
Felix,

[moving from oozie-users@  (in BCC) to cdh-user@ alias as this seems a CDH setup  problem]

If you are using RPM CDH Hadoop and Oozie, you don't have to modify the HadoopAccessorService.

Everything should work out of the box with zero configuration.

Would you try to revert to a clean install and see if you have issues there?

Thxs.

Alejandro



On Wed, Aug 24, 2011 at 11:15 AM, Felix <felixgao@...> wrote:
Alejandro,

I am modifying the oozie.services to
<property>
       <name>oozie.services</name>
       <value>
           org.apache.oozie.service.SchedulerService,
           org.apache.oozie.service.InstrumentationService,
           org.apache.oozie.service.CallableQueueService,
           org.apache.oozie.service.UUIDService,
           org.apache.oozie.service.ELService,
           org.apache.oozie.service.AuthorizationService,
           org.apache.oozie.service.MemoryLocksService,
           org.apache.oozie.service.DagXLogInfoService,
           org.apache.oozie.service.SchemaService,
           org.apache.oozie.service.LiteWorkflowAppService,
           org.apache.oozie.service.StoreService,
           org.apache.oozie.service.CoordinatorStoreService,
           org.apache.oozie.service.SLAStoreService,
           org.apache.oozie.service.DBLiteWorkflowStoreService,
           org.apache.oozie.service.CallbackService,
           org.apache.oozie.service.ActionService,
           org.apache.oozie.service.ActionCheckerService,
           org.apache.oozie.service.RecoveryService,
           org.apache.oozie.service.PurgeService,
           org.apache.oozie.service.CoordinatorEngineService,
           org.apache.oozie.service.DagEngineService,
           org.apache.oozie.service.CoordJobMatLookupTriggerService,
           org.apache.oozie.service.HadoopAccessorService
       </value>
       <description>
           All services to be created and managed by Oozie Services singleton.
           Class names must be separated by commas.
       </description>
   </property>

because I am seeing E0902: Exception occured:  so https://github.com/yahoo/oozie/wiki/FAQ told me to add those to the xml file.

--- In Oozie-users@yahoogroups.com, Alejandro Abdelnur <tucu@...> wrote:
>
> Felix,
>
> What are doing that you need to modify the service classes?
>
> Thanks.
>
> Alejandro
>
> On Wed, Aug 24, 2011 at 9:53 AM, Felix <felixgao@...> wrote:
>
> > NN is running on a different box and so is JT. I do have access to NN and
> > JT from localhost, the box that is used for oozie used to be the launchpad
> > for all of our pig jobs.  When I do hadoop fs I will be able to view the
> > HDFS for which ever user that I am logged in with.
> >
> > For my test pig I only have the following in the HDFS
> > hadoop fs -ls /user/felix/oozie/workflows/test_pig
> > Found 2 items
> > -rw-r--r--   2 felix supergroup        367 2011-08-23 14:28
> > /user/felix/oozie/workflows/test_pig/config-default.xml
> > drwxr-xr-x   - felix supergroup          0 2011-08-23 14:08
> > /user/felix/oozie/workflows/test_pig/lib
> >
> >
> > The lib is empty right now.
> > In my local directory I have
> > ls -al
> > total 28
> > drwxrwxr-x 2 felix felix 4096 Aug 23 16:14 .
> > drwxrwxr-x 3 felix felix 4096 Aug 23 13:07 ..
> > -rw-rw-r-- 1 felix felix  367 Aug 23 14:28 config-default.xml
> > -rw-rw-r-- 1 felix felix  486 Aug 23 15:56 job.properties
> > -rw-rw-r-- 1 felix felix  309 Aug 23 15:02 pigexample.pig
> > -rw-rw-r-- 1 felix felix 1190 Aug 23 15:41 pig-wf.xml
> > -rwxrwxrwx 1 felix felix  929 Aug 23 16:09 submit.sh
> >
> >  cat job.properties
> > #The following attributes must be set
> > fs.default.name=hdfs://namenode.xxx.xxx:50001
> > mapred.job.tracker=jobtracker.xxx.xxx:50002
> > oozie.use.system.libpath=true
> > oozie.libpath=hdfs://namenode.xxx.xxx:50001/user/oozie/share/pig/lib/
> > queueName=default
> > #additional
> >
> > oozie.wf.application.path=hdfs://namenode.xxx.xxx:50001/user/felix/oozie/workflows/test_pig
> > inputDir=/user/felix/test_input.data
> > outputDir=/user/felix/oozie_output/pig_test
> >
> > I submitted the job to Oozie using
> > oozie pig -oozie http://localhost:11000/oozie -file pigexample.pig -config
> > job.properties
> >
> > hadoop we are using is 0.20.2 and oozie we are using is 2.3.0. Both are
> > from cloudera's RPM.
> >
> > I hope this is clear enough.
> >
> > --- In Oozie-users@yahoogroups.com, Mohammad Islam <mislam77@> wrote:
> > >
> > > Do you have the NN running on the same box?
> > >
> > > If not,  do you have the access from the localhost to NN? Did you able
> > to run "haddop fs ..." command from the localhost?
> > >
> > >
> > > Which version of hadoop and what version of oozie you are using?
> > > What is the wf apppath in job.properties?
> > >
> > > Regards,
> > > Mohammad
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: Felix <felixgao@>
> > > To: Oozie-users@yahoogroups.com
> > > Sent: Tuesday, August 23, 2011 3:28 PM
> > > Subject: [Oozie-users] Oozie error when submitting jobs
> > >
> > >
> > > Â
> > > Hi all I have a simple pig job for testing that I would like to use oozie
> > to manage.  When I do the following I got
> > >
> > > oozie pig -oozie http://localhost:11000/oozie -file pigexample.pig
> > -config job.properties
> > > Error: E0902 : E0902: Exception occured: [java.io.IOException: Call to
> > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > java.io.EOFException]
> > >
> > > 2011-08-23 17:18:11,861  WARN V1JobsServlet:528 - USER[felix]
> > GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
> > http://localhost:11000/oozie/v1/jobs?jobtype=pig] error[E0902], E0902:
> > Exception occured: [java.io.IOException: Call to
> > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > java.io.EOFException]
> > > org.apache.oozie.servlet.XServletException: E0902: Exception occured:
> > [java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed on local
> > exception: java.io.EOFException]
> > > at
> > org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:179)
> > > at
> > org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> > > at
> > org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> > > at
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> > > at
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> > > at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> > > at
> > com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:371)
> > > at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> > > at
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> > > at
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> > > at
> > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> > > at
> > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> > > at
> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> > > at
> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> > > at
> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> > > at
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> > > at
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> > > at
> > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> > > at
> > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> > > at java.lang.Thread.run(Thread.java:619)
> > > Caused by: org.apache.oozie.service.AuthorizationException: E0902:
> > Exception occured: [java.io.IOException: Call to
> > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > java.io.EOFException]
> > > at
> > org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:318)
> > > at
> > org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:171)
> > > ... 21 more
> > > Caused by: org.apache.oozie.service.HadoopAccessorException: E0902:
> > Exception occured: [java.io.IOException: Call to
> > namenode.chi.bluekai.com/69.170.130.176:50001 failed on local exception:
> > java.io.EOFException]
> > > at
> > org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorService.java:144)
> > > at
> > org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:283)
> > > ... 22 more
> > > Caused by: java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001
> > failed on local exception: java.io.EOFException
> > > at org.apache.hadoop.ipc.Client.wrapException(Client.java:1142)
> > > at org.apache.hadoop.ipc.Client.call(Client.java:1110)
> > > at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:226)
> > > at $Proxy22.getProtocolVersion(Unknown Source)
> > > at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:398)
> > > at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:384)
> > > at org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:111)
> > > at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:213)
> > > at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:180)
> > > at
> > org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:89)
> > > at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1514)
> > > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:67)
> > > at
> > org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:1548)
> > > at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1530)
> > > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:228)
> > > at
> > org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorService.java:141)
> > > ... 23 more
> > > Caused by: java.io.EOFException
> > > at java.io.DataInputStream.readInt(DataInputStream.java:375)
> > > at
> > org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:815)
> > > at org.apache.hadoop.ipc.Client$Connection.run(Client.java:724)
> > >
> > > in my oozie-site.xml I have the following services
> > > <property>
> > > <name>oozie.services</name>
> > > <value>
> > > org.apache.oozie.service.SchedulerService,
> > > org.apache.oozie.service.InstrumentationService,
> > > org.apache.oozie.service.CallableQueueService,
> > > org.apache.oozie.service.UUIDService,
> > > org.apache.oozie.service.ELService,
> > > org.apache.oozie.service.AuthorizationService,
> > > org.apache.oozie.service.MemoryLocksService,
> > > org.apache.oozie.service.DagXLogInfoService,
> > > org.apache.oozie.service.SchemaService,
> > > org.apache.oozie.service.LiteWorkflowAppService,
> > > org.apache.oozie.service.StoreService,
> > > org.apache.oozie.service.CoordinatorStoreService,
> > > org.apache.oozie.service.SLAStoreService,
> > > org.apache.oozie.service.DBLiteWorkflowStoreService,
> > > org.apache.oozie.service.CallbackService,
> > > org.apache.oozie.service.ActionService,
> > > org.apache.oozie.service.ActionCheckerService,
> > > org.apache.oozie.service.RecoveryService,
> > > org.apache.oozie.service.PurgeService,
> > > org.apache.oozie.service.CoordinatorEngineService,
> > > org.apache.oozie.service.DagEngineService,
> > > org.apache.oozie.service.CoordJobMatLookupTriggerService,
> > > org.apache.oozie.service.HadoopAccessorService
> > > </value>
> > > <description>
> > > All services to be created and managed by Oozie Services singleton.
> > > Class names must be separated by commas.
> > > </description>
> > > </property>
> > >
> > > if I take out org.apache.oozie.service.HadoopAccessorService, then I will
> > get
> > > 2011-08-23 16:09:45,587 ERROR V1JobsServlet:522 - USER[felix]
> > GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
> > http://localhost:11000/oozie/v1/jobs?jobtype=pig] error, null
> > > java.lang.NullPointerException
> > > at
> > org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:283)
> > > at
> > org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:171)
> > > at
> > org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> > > at
> > org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> > > at
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> > > at
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> > > at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> > > at
> > com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:371)
> > > at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> > > at
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> > > at
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> > > at
> > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> > > at
> > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> > > at
> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> > > at
> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> > > at
> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> > > at
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> > > at
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> > > at
> > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> > > at
> > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> > > at java.lang.Thread.run(Thread.java:619)
> > >
> > > your help is appreciated.
> > >
> > > Felix
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>




------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
   http://groups.yahoo.com/group/Oozie-users/

<*> Your email settings:
   Individual Email | Traditional

<*> To change settings online go to:
   http://groups.yahoo.com/group/Oozie-users/join
   (Yahoo! ID required)

<*> To change settings via email:
   Oozie-users-digest@yahoogroups.com
   Oozie-users-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
   Oozie-users-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
   http://docs.yahoo.com/info/terms/



#2026 From: "Felix" <felixgao@...>
Date: Wed Aug 24, 2011 7:01 pm
Subject: Re: Oozie error when submitting jobs
felixgao
Send Email Send Email
 
When reverted to the stock oozie-site.xml except I have changed the database to
use mysql instead of derby. I still have the exception below.

2011-08-24 13:58:40,107  WARN V1JobsServlet:528 - USER[felix] GROUP[users]
TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
http://localhost:11000/oozie/v1/jobs?jobtype=pig] error[E0902], E0902: Exception
occured: [java.io.IOException: Call to namenode.xxx/69.xxx.xxx.xxx:50001 failed
on local exception: java.io.EOFException]
org.apache.oozie.servlet.XServletException: E0902: Exception occured:
[java.io.IOException: Call to namenode.xxx/69.xxx.xxx.xxx:50001 failed on local
exception: java.io.EOFException]
	 at
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:179)
	 at org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
	 at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
	 at org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
	 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:290)
	 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
	 at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
	 at
com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.j\
ava:371)
	 at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
	 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:235)
	 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
	 at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2\
33)
	 at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1\
91)
	 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
	 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	 at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109\
)
	 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
	 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
	 at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Pr\
otocol.java:588)
	 at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
	 at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.oozie.service.AuthorizationException: E0902: Exception
occured: [java.io.IOException: Call to namenode.xxx/69.xxx.xxx.xxx:50001 failed
on local exception: java.io.EOFException]
	 at
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:318)
	 at
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:171)
	 ... 21 more
Caused by: org.apache.oozie.service.HadoopAccessorException: E0902: Exception
occured: [java.io.IOException: Call to
namenode.chi.bluekai.com/69.170.130.176:50001 failed on local exception:
java.io.EOFException]
	 at
org.apache.oozie.service.KerberosHadoopAccessorService.createFileSystem(Kerberos\
HadoopAccessorService.java:211)
	 at
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:283)
	 ... 22 more
Caused by: java.io.IOException: Call to namenode.xxx/69.xxx.xxx.xxx:50001 failed
on local exception: java.io.EOFException
	 at org.apache.hadoop.ipc.Client.wrapException(Client.java:1142)
	 at org.apache.hadoop.ipc.Client.call(Client.java:1110)
	 at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:226)
	 at $Proxy22.getProtocolVersion(Unknown Source)
	 at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:398)
	 at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:384)
	 at org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:111)
	 at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:213)
	 at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:180)
	 at
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.ja\
va:89)
	 at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1514)
	 at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:67)
	 at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:1548)
	 at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1530)
	 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:228)
	 at
org.apache.oozie.service.KerberosHadoopAccessorService$3.run(KerberosHadoopAcces\
sorService.java:203)
	 at
org.apache.oozie.service.KerberosHadoopAccessorService$3.run(KerberosHadoopAcces\
sorService.java:194)
	 at java.security.AccessController.doPrivileged(Native Method)
	 at javax.security.auth.Subject.doAs(Subject.java:396)
	 at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1\
127)
	 at
org.apache.oozie.service.KerberosHadoopAccessorService.createFileSystem(Kerberos\
HadoopAccessorService.java:194)
	 ... 23 more
Caused by: java.io.EOFException
	 at java.io.DataInputStream.readInt(DataInputStream.java:375)
	 at org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:815)
	 at org.apache.hadoop.ipc.Client$Connection.run(Client.java:724)



--- In Oozie-users@yahoogroups.com, Alejandro Abdelnur <tucu@...> wrote:
>
> Felix,
>
> [moving from oozie-users@  (in BCC) to cdh-user@ alias as this seems a CDH
> setup  problem]
>
> If you are using RPM CDH Hadoop and Oozie, you don't have to modify the
> HadoopAccessorService.
>
> Everything should work out of the box with zero configuration.
>
> Would you try to revert to a clean install and see if you have issues there?
>
> Thxs.
>
> Alejandro
>
>
>
> On Wed, Aug 24, 2011 at 11:15 AM, Felix <felixgao@...> wrote:
>
> > Alejandro,
> >
> > I am modifying the oozie.services to
> > <property>
> >        <name>oozie.services</name>
> >        <value>
> >            org.apache.oozie.service.SchedulerService,
> >            org.apache.oozie.service.InstrumentationService,
> >            org.apache.oozie.service.CallableQueueService,
> >            org.apache.oozie.service.UUIDService,
> >            org.apache.oozie.service.ELService,
> >            org.apache.oozie.service.AuthorizationService,
> >            org.apache.oozie.service.MemoryLocksService,
> >            org.apache.oozie.service.DagXLogInfoService,
> >            org.apache.oozie.service.SchemaService,
> >            org.apache.oozie.service.LiteWorkflowAppService,
> >            org.apache.oozie.service.StoreService,
> >            org.apache.oozie.service.CoordinatorStoreService,
> >            org.apache.oozie.service.SLAStoreService,
> >            org.apache.oozie.service.DBLiteWorkflowStoreService,
> >            org.apache.oozie.service.CallbackService,
> >            org.apache.oozie.service.ActionService,
> >            org.apache.oozie.service.ActionCheckerService,
> >            org.apache.oozie.service.RecoveryService,
> >            org.apache.oozie.service.PurgeService,
> >            org.apache.oozie.service.CoordinatorEngineService,
> >            org.apache.oozie.service.DagEngineService,
> >            org.apache.oozie.service.CoordJobMatLookupTriggerService,
> >            org.apache.oozie.service.HadoopAccessorService
> >        </value>
> >        <description>
> >            All services to be created and managed by Oozie Services
> > singleton.
> >            Class names must be separated by commas.
> >        </description>
> >    </property>
> >
> > because I am seeing E0902: Exception occured:  so
> > https://github.com/yahoo/oozie/wiki/FAQ told me to add those to the xml
> > file.
> >
> > --- In Oozie-users@yahoogroups.com, Alejandro Abdelnur <tucu@> wrote:
> > >
> > > Felix,
> > >
> > > What are doing that you need to modify the service classes?
> > >
> > > Thanks.
> > >
> > > Alejandro
> > >
> > > On Wed, Aug 24, 2011 at 9:53 AM, Felix <felixgao@> wrote:
> > >
> > > > NN is running on a different box and so is JT. I do have access to NN
> > and
> > > > JT from localhost, the box that is used for oozie used to be the
> > launchpad
> > > > for all of our pig jobs.  When I do hadoop fs I will be able to view
> > the
> > > > HDFS for which ever user that I am logged in with.
> > > >
> > > > For my test pig I only have the following in the HDFS
> > > > hadoop fs -ls /user/felix/oozie/workflows/test_pig
> > > > Found 2 items
> > > > -rw-r--r--   2 felix supergroup        367 2011-08-23 14:28
> > > > /user/felix/oozie/workflows/test_pig/config-default.xml
> > > > drwxr-xr-x   - felix supergroup          0 2011-08-23 14:08
> > > > /user/felix/oozie/workflows/test_pig/lib
> > > >
> > > >
> > > > The lib is empty right now.
> > > > In my local directory I have
> > > > ls -al
> > > > total 28
> > > > drwxrwxr-x 2 felix felix 4096 Aug 23 16:14 .
> > > > drwxrwxr-x 3 felix felix 4096 Aug 23 13:07 ..
> > > > -rw-rw-r-- 1 felix felix  367 Aug 23 14:28 config-default.xml
> > > > -rw-rw-r-- 1 felix felix  486 Aug 23 15:56 job.properties
> > > > -rw-rw-r-- 1 felix felix  309 Aug 23 15:02 pigexample.pig
> > > > -rw-rw-r-- 1 felix felix 1190 Aug 23 15:41 pig-wf.xml
> > > > -rwxrwxrwx 1 felix felix  929 Aug 23 16:09 submit.sh
> > > >
> > > >  cat job.properties
> > > > #The following attributes must be set
> > > > fs.default.name=hdfs://namenode.xxx.xxx:50001
> > > > mapred.job.tracker=jobtracker.xxx.xxx:50002
> > > > oozie.use.system.libpath=true
> > > > oozie.libpath=hdfs://namenode.xxx.xxx:50001/user/oozie/share/pig/lib/
> > > > queueName=default
> > > > #additional
> > > >
> > > >
> >
oozie.wf.application.path=hdfs://namenode.xxx.xxx:50001/user/felix/oozie/workflo\
ws/test_pig
> > > > inputDir=/user/felix/test_input.data
> > > > outputDir=/user/felix/oozie_output/pig_test
> > > >
> > > > I submitted the job to Oozie using
> > > > oozie pig -oozie http://localhost:11000/oozie -file pigexample.pig
> > -config
> > > > job.properties
> > > >
> > > > hadoop we are using is 0.20.2 and oozie we are using is 2.3.0. Both are
> > > > from cloudera's RPM.
> > > >
> > > > I hope this is clear enough.
> > > >
> > > > --- In Oozie-users@yahoogroups.com, Mohammad Islam <mislam77@> wrote:
> > > > >
> > > > > Do you have the NN running on the same box?
> > > > >
> > > > > If not,  do you have the access from the localhost to NN? Did you
> > able
> > > > to run "haddop fs ..." command from the localhost?
> > > > >
> > > > >
> > > > > Which version of hadoop and what version of oozie you are using?
> > > > > What is the wf apppath in job.properties?
> > > > >
> > > > > Regards,
> > > > > Mohammad
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: Felix <felixgao@>
> > > > > To: Oozie-users@yahoogroups.com
> > > > > Sent: Tuesday, August 23, 2011 3:28 PM
> > > > > Subject: [Oozie-users] Oozie error when submitting jobs
> > > > >
> > > > >
> > > > > Â
> > > > > Hi all I have a simple pig job for testing that I would like to use
> > oozie
> > > > to manage.  When I do the following I got
> > > > >
> > > > > oozie pig -oozie http://localhost:11000/oozie -file pigexample.pig
> > > > -config job.properties
> > > > > Error: E0902 : E0902: Exception occured: [java.io.IOException: Call
> > to
> > > > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > > > java.io.EOFException]
> > > > >
> > > > > 2011-08-23 17:18:11,861  WARN V1JobsServlet:528 - USER[felix]
> > > > GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
> > > > http://localhost:11000/oozie/v1/jobs?jobtype=pig] error[E0902], E0902:
> > > > Exception occured: [java.io.IOException: Call to
> > > > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > > > java.io.EOFException]
> > > > > org.apache.oozie.servlet.XServletException: E0902: Exception occured:
> > > > [java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed on
> > local
> > > > exception: java.io.EOFException]
> > > > > at
> > > >
> >
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:179)
> > > > > at
> > > >
> > org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> > > > > at
> > > >
> > org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> > > > > at
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:290)
> > > > > at
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> > > > > at
> > org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> > > > > at
> > > >
> >
com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.j\
ava:371)
> > > > > at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> > > > > at
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:235)
> > > > > at
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> > > > > at
> > > >
> >
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2\
33)
> > > > > at
> > > >
> >
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1\
91)
> > > > > at
> > > >
> >
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> > > > > at
> > > >
> >
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> > > > > at
> > > >
> >
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109\
)
> > > > > at
> > > >
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> > > > > at
> > > >
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> > > > > at
> > > >
> >
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Pr\
otocol.java:588)
> > > > > at
> > > > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> > > > > at java.lang.Thread.run(Thread.java:619)
> > > > > Caused by: org.apache.oozie.service.AuthorizationException: E0902:
> > > > Exception occured: [java.io.IOException: Call to
> > > > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > > > java.io.EOFException]
> > > > > at
> > > >
> >
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:318)
> > > > > at
> > > >
> >
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:171)
> > > > > ... 21 more
> > > > > Caused by: org.apache.oozie.service.HadoopAccessorException: E0902:
> > > > Exception occured: [java.io.IOException: Call to
> > > > namenode.chi.bluekai.com/69.170.130.176:50001 failed on local
> > exception:
> > > > java.io.EOFException]
> > > > > at
> > > >
> >
org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorSe\
rvice.java:144)
> > > > > at
> > > >
> >
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:283)
> > > > > ... 22 more
> > > > > Caused by: java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001
> > > > failed on local exception: java.io.EOFException
> > > > > at org.apache.hadoop.ipc.Client.wrapException(Client.java:1142)
> > > > > at org.apache.hadoop.ipc.Client.call(Client.java:1110)
> > > > > at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:226)
> > > > > at $Proxy22.getProtocolVersion(Unknown Source)
> > > > > at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:398)
> > > > > at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:384)
> > > > > at
> > org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:111)
> > > > > at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:213)
> > > > > at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:180)
> > > > > at
> > > >
> >
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.ja\
va:89)
> > > > > at
> > org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1514)
> > > > > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:67)
> > > > > at
> > > > org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:1548)
> > > > > at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1530)
> > > > > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:228)
> > > > > at
> > > >
> >
org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorSe\
rvice.java:141)
> > > > > ... 23 more
> > > > > Caused by: java.io.EOFException
> > > > > at java.io.DataInputStream.readInt(DataInputStream.java:375)
> > > > > at
> > > >
> > org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:815)
> > > > > at org.apache.hadoop.ipc.Client$Connection.run(Client.java:724)
> > > > >
> > > > > in my oozie-site.xml I have the following services
> > > > > <property>
> > > > > <name>oozie.services</name>
> > > > > <value>
> > > > > org.apache.oozie.service.SchedulerService,
> > > > > org.apache.oozie.service.InstrumentationService,
> > > > > org.apache.oozie.service.CallableQueueService,
> > > > > org.apache.oozie.service.UUIDService,
> > > > > org.apache.oozie.service.ELService,
> > > > > org.apache.oozie.service.AuthorizationService,
> > > > > org.apache.oozie.service.MemoryLocksService,
> > > > > org.apache.oozie.service.DagXLogInfoService,
> > > > > org.apache.oozie.service.SchemaService,
> > > > > org.apache.oozie.service.LiteWorkflowAppService,
> > > > > org.apache.oozie.service.StoreService,
> > > > > org.apache.oozie.service.CoordinatorStoreService,
> > > > > org.apache.oozie.service.SLAStoreService,
> > > > > org.apache.oozie.service.DBLiteWorkflowStoreService,
> > > > > org.apache.oozie.service.CallbackService,
> > > > > org.apache.oozie.service.ActionService,
> > > > > org.apache.oozie.service.ActionCheckerService,
> > > > > org.apache.oozie.service.RecoveryService,
> > > > > org.apache.oozie.service.PurgeService,
> > > > > org.apache.oozie.service.CoordinatorEngineService,
> > > > > org.apache.oozie.service.DagEngineService,
> > > > > org.apache.oozie.service.CoordJobMatLookupTriggerService,
> > > > > org.apache.oozie.service.HadoopAccessorService
> > > > > </value>
> > > > > <description>
> > > > > All services to be created and managed by Oozie Services singleton.
> > > > > Class names must be separated by commas.
> > > > > </description>
> > > > > </property>
> > > > >
> > > > > if I take out org.apache.oozie.service.HadoopAccessorService, then I
> > will
> > > > get
> > > > > 2011-08-23 16:09:45,587 ERROR V1JobsServlet:522 - USER[felix]
> > > > GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
> > > > http://localhost:11000/oozie/v1/jobs?jobtype=pig] error, null
> > > > > java.lang.NullPointerException
> > > > > at
> > > >
> >
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:283)
> > > > > at
> > > >
> >
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:171)
> > > > > at
> > > >
> > org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> > > > > at
> > > >
> > org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> > > > > at
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:290)
> > > > > at
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> > > > > at
> > org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> > > > > at
> > > >
> >
com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.j\
ava:371)
> > > > > at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> > > > > at
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:235)
> > > > > at
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> > > > > at
> > > >
> >
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2\
33)
> > > > > at
> > > >
> >
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1\
91)
> > > > > at
> > > >
> >
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> > > > > at
> > > >
> >
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> > > > > at
> > > >
> >
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109\
)
> > > > > at
> > > >
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> > > > > at
> > > >
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> > > > > at
> > > >
> >
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Pr\
otocol.java:588)
> > > > > at
> > > > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> > > > > at java.lang.Thread.run(Thread.java:619)
> > > > >
> > > > > your help is appreciated.
> > > > >
> > > > > Felix
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>

#2027 From: Alejandro Abdelnur <tucu@...>
Date: Wed Aug 24, 2011 7:10 pm
Subject: Re: Re: Oozie error when submitting jobs
tucu0
Send Email Send Email
 
Felix,

[Again, moving to the cdh-user@ alias, BCCing oozie-users]

What are the exact versions of Hadoop and Oozie you are using?

What unix user is running Oozie server? 

How are you starting Oozier server?

Can you send the configuration of your Hadoop core-site.xml? I just care about the properties that have 'proxyuser' in their name.

Thanks.

Alejandro

On Wed, Aug 24, 2011 at 12:01 PM, Felix <felixgao@...> wrote:
When reverted to the stock oozie-site.xml except I have changed the database to use mysql instead of derby. I still have the exception below.

2011-08-24 13:58:40,107  WARN V1JobsServlet:528 - USER[felix] GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST http://localhost:11000/oozie/v1/jobs?jobtype=pig] error[E0902], E0902: Exception occured: [java.io.IOException: Call to namenode.xxx/69.xxx.xxx.xxx:50001 failed on local exception: java.io.EOFException]
org.apache.oozie.servlet.XServletException: E0902: Exception occured: [java.io.IOException: Call to namenode.xxx/69.xxx.xxx.xxx:50001 failed on local exception: java.io.EOFException]
       at org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:179)
       at org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
       at org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
       at com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:371)
       at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
       at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.oozie.service.AuthorizationException: E0902: Exception occured: [java.io.IOException: Call to namenode.xxx/69.xxx.xxx.xxx:50001 failed on local exception: java.io.EOFException]
       at org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:318)
       at org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:171)
       ... 21 more
Caused by: org.apache.oozie.service.HadoopAccessorException: E0902: Exception occured: [java.io.IOException: Call to namenode.chi.bluekai.com/69.170.130.176:50001 failed on local exception: java.io.EOFException]
       at org.apache.oozie.service.KerberosHadoopAccessorService.createFileSystem(KerberosHadoopAccessorService.java:211)
       at org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:283)
       ... 22 more
Caused by: java.io.IOException: Call to namenode.xxx/69.xxx.xxx.xxx:50001 failed on local exception: java.io.EOFException
       at org.apache.hadoop.ipc.Client.wrapException(Client.java:1142)
       at org.apache.hadoop.ipc.Client.call(Client.java:1110)
       at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:226)
       at $Proxy22.getProtocolVersion(Unknown Source)
       at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:398)
       at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:384)
       at org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:111)
       at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:213)
       at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:180)
       at org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:89)
       at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1514)
       at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:67)
       at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:1548)
       at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1530)
       at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:228)
       at org.apache.oozie.service.KerberosHadoopAccessorService$3.run(KerberosHadoopAccessorService.java:203)
       at org.apache.oozie.service.KerberosHadoopAccessorService$3.run(KerberosHadoopAccessorService.java:194)
       at java.security.AccessController.doPrivileged(Native Method)
       at javax.security.auth.Subject.doAs(Subject.java:396)
       at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1127)
       at org.apache.oozie.service.KerberosHadoopAccessorService.createFileSystem(KerberosHadoopAccessorService.java:194)
       ... 23 more
Caused by: java.io.EOFException
       at java.io.DataInputStream.readInt(DataInputStream.java:375)
       at org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:815)
       at org.apache.hadoop.ipc.Client$Connection.run(Client.java:724)



--- In Oozie-users@yahoogroups.com, Alejandro Abdelnur <tucu@...> wrote:
>
> Felix,
>
> [moving from oozie-users@  (in BCC) to cdh-user@ alias as this seems a CDH
> setup  problem]
>
> If you are using RPM CDH Hadoop and Oozie, you don't have to modify the
> HadoopAccessorService.
>
> Everything should work out of the box with zero configuration.
>
> Would you try to revert to a clean install and see if you have issues there?
>
> Thxs.
>
> Alejandro
>
>
>
> On Wed, Aug 24, 2011 at 11:15 AM, Felix <felixgao@...> wrote:
>
> > Alejandro,
> >
> > I am modifying the oozie.services to
> > <property>
> >        <name>oozie.services</name>
> >        <value>
> >            org.apache.oozie.service.SchedulerService,
> >            org.apache.oozie.service.InstrumentationService,
> >            org.apache.oozie.service.CallableQueueService,
> >            org.apache.oozie.service.UUIDService,
> >            org.apache.oozie.service.ELService,
> >            org.apache.oozie.service.AuthorizationService,
> >            org.apache.oozie.service.MemoryLocksService,
> >            org.apache.oozie.service.DagXLogInfoService,
> >            org.apache.oozie.service.SchemaService,
> >            org.apache.oozie.service.LiteWorkflowAppService,
> >            org.apache.oozie.service.StoreService,
> >            org.apache.oozie.service.CoordinatorStoreService,
> >            org.apache.oozie.service.SLAStoreService,
> >            org.apache.oozie.service.DBLiteWorkflowStoreService,
> >            org.apache.oozie.service.CallbackService,
> >            org.apache.oozie.service.ActionService,
> >            org.apache.oozie.service.ActionCheckerService,
> >            org.apache.oozie.service.RecoveryService,
> >            org.apache.oozie.service.PurgeService,
> >            org.apache.oozie.service.CoordinatorEngineService,
> >            org.apache.oozie.service.DagEngineService,
> >            org.apache.oozie.service.CoordJobMatLookupTriggerService,
> >            org.apache.oozie.service.HadoopAccessorService
> >        </value>
> >        <description>
> >            All services to be created and managed by Oozie Services
> > singleton.
> >            Class names must be separated by commas.
> >        </description>
> >    </property>
> >
> > because I am seeing E0902: Exception occured:  so
> > https://github.com/yahoo/oozie/wiki/FAQ told me to add those to the xml
> > file.
> >
> > --- In Oozie-users@yahoogroups.com, Alejandro Abdelnur <tucu@> wrote:
> > >
> > > Felix,
> > >
> > > What are doing that you need to modify the service classes?
> > >
> > > Thanks.
> > >
> > > Alejandro
> > >
> > > On Wed, Aug 24, 2011 at 9:53 AM, Felix <felixgao@> wrote:
> > >
> > > > NN is running on a different box and so is JT. I do have access to NN
> > and
> > > > JT from localhost, the box that is used for oozie used to be the
> > launchpad
> > > > for all of our pig jobs.  When I do hadoop fs I will be able to view
> > the
> > > > HDFS for which ever user that I am logged in with.
> > > >
> > > > For my test pig I only have the following in the HDFS
> > > > hadoop fs -ls /user/felix/oozie/workflows/test_pig
> > > > Found 2 items
> > > > -rw-r--r--   2 felix supergroup        367 2011-08-23 14:28
> > > > /user/felix/oozie/workflows/test_pig/config-default.xml
> > > > drwxr-xr-x   - felix supergroup          0 2011-08-23 14:08
> > > > /user/felix/oozie/workflows/test_pig/lib
> > > >
> > > >
> > > > The lib is empty right now.
> > > > In my local directory I have
> > > > ls -al
> > > > total 28
> > > > drwxrwxr-x 2 felix felix 4096 Aug 23 16:14 .
> > > > drwxrwxr-x 3 felix felix 4096 Aug 23 13:07 ..
> > > > -rw-rw-r-- 1 felix felix  367 Aug 23 14:28 config-default.xml
> > > > -rw-rw-r-- 1 felix felix  486 Aug 23 15:56 job.properties
> > > > -rw-rw-r-- 1 felix felix  309 Aug 23 15:02 pigexample.pig
> > > > -rw-rw-r-- 1 felix felix 1190 Aug 23 15:41 pig-wf.xml
> > > > -rwxrwxrwx 1 felix felix  929 Aug 23 16:09 submit.sh
> > > >
> > > >  cat job.properties
> > > > #The following attributes must be set
> > > > fs.default.name=hdfs://namenode.xxx.xxx:50001
> > > > mapred.job.tracker=jobtracker.xxx.xxx:50002
> > > > oozie.use.system.libpath=true
> > > > oozie.libpath=hdfs://namenode.xxx.xxx:50001/user/oozie/share/pig/lib/
> > > > queueName=default
> > > > #additional
> > > >
> > > >
> > oozie.wf.application.path=hdfs://namenode.xxx.xxx:50001/user/felix/oozie/workflows/test_pig
> > > > inputDir=/user/felix/test_input.data
> > > > outputDir=/user/felix/oozie_output/pig_test
> > > >
> > > > I submitted the job to Oozie using
> > > > oozie pig -oozie http://localhost:11000/oozie -file pigexample.pig
> > -config
> > > > job.properties
> > > >
> > > > hadoop we are using is 0.20.2 and oozie we are using is 2.3.0. Both are
> > > > from cloudera's RPM.
> > > >
> > > > I hope this is clear enough.
> > > >
> > > > --- In Oozie-users@yahoogroups.com, Mohammad Islam <mislam77@> wrote:
> > > > >
> > > > > Do you have the NN running on the same box?
> > > > >
> > > > > If not,  do you have the access from the localhost to NN? Did you
> > able
> > > > to run "haddop fs ..." command from the localhost?
> > > > >
> > > > >
> > > > > Which version of hadoop and what version of oozie you are using?
> > > > > What is the wf apppath in job.properties?
> > > > >
> > > > > Regards,
> > > > > Mohammad
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: Felix <felixgao@>
> > > > > To: Oozie-users@yahoogroups.com
> > > > > Sent: Tuesday, August 23, 2011 3:28 PM
> > > > > Subject: [Oozie-users] Oozie error when submitting jobs
> > > > >
> > > > >
> > > > > Â
> > > > > Hi all I have a simple pig job for testing that I would like to use
> > oozie
> > > > to manage.  When I do the following I got
> > > > >
> > > > > oozie pig -oozie http://localhost:11000/oozie -file pigexample.pig
> > > > -config job.properties
> > > > > Error: E0902 : E0902: Exception occured: [java.io.IOException: Call
> > to
> > > > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > > > java.io.EOFException]
> > > > >
> > > > > 2011-08-23 17:18:11,861  WARN V1JobsServlet:528 - USER[felix]
> > > > GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
> > > > http://localhost:11000/oozie/v1/jobs?jobtype=pig] error[E0902], E0902:
> > > > Exception occured: [java.io.IOException: Call to
> > > > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > > > java.io.EOFException]
> > > > > org.apache.oozie.servlet.XServletException: E0902: Exception occured:
> > > > [java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed on
> > local
> > > > exception: java.io.EOFException]
> > > > > at
> > > >
> > org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:179)
> > > > > at
> > > >
> > org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> > > > > at
> > > >
> > org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> > > > > at
> > > >
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> > > > > at
> > > >
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> > > > > at
> > org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> > > > > at
> > > >
> > com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:371)
> > > > > at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> > > > > at
> > > >
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> > > > > at
> > > >
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> > > > > at
> > > >
> > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> > > > > at
> > > >
> > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> > > > > at
> > > >
> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> > > > > at
> > > >
> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> > > > > at
> > > >
> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> > > > > at
> > > >
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> > > > > at
> > > >
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> > > > > at
> > > >
> > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> > > > > at
> > > > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> > > > > at java.lang.Thread.run(Thread.java:619)
> > > > > Caused by: org.apache.oozie.service.AuthorizationException: E0902:
> > > > Exception occured: [java.io.IOException: Call to
> > > > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > > > java.io.EOFException]
> > > > > at
> > > >
> > org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:318)
> > > > > at
> > > >
> > org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:171)
> > > > > ... 21 more
> > > > > Caused by: org.apache.oozie.service.HadoopAccessorException: E0902:
> > > > Exception occured: [java.io.IOException: Call to
> > > > namenode.chi.bluekai.com/69.170.130.176:50001 failed on local
> > exception:
> > > > java.io.EOFException]
> > > > > at
> > > >
> > org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorService.java:144)
> > > > > at
> > > >
> > org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:283)
> > > > > ... 22 more
> > > > > Caused by: java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001
> > > > failed on local exception: java.io.EOFException
> > > > > at org.apache.hadoop.ipc.Client.wrapException(Client.java:1142)
> > > > > at org.apache.hadoop.ipc.Client.call(Client.java:1110)
> > > > > at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:226)
> > > > > at $Proxy22.getProtocolVersion(Unknown Source)
> > > > > at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:398)
> > > > > at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:384)
> > > > > at
> > org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:111)
> > > > > at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:213)
> > > > > at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:180)
> > > > > at
> > > >
> > org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:89)
> > > > > at
> > org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1514)
> > > > > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:67)
> > > > > at
> > > > org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:1548)
> > > > > at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1530)
> > > > > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:228)
> > > > > at
> > > >
> > org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorService.java:141)
> > > > > ... 23 more
> > > > > Caused by: java.io.EOFException
> > > > > at java.io.DataInputStream.readInt(DataInputStream.java:375)
> > > > > at
> > > >
> > org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:815)
> > > > > at org.apache.hadoop.ipc.Client$Connection.run(Client.java:724)
> > > > >
> > > > > in my oozie-site.xml I have the following services
> > > > > <property>
> > > > > <name>oozie.services</name>
> > > > > <value>
> > > > > org.apache.oozie.service.SchedulerService,
> > > > > org.apache.oozie.service.InstrumentationService,
> > > > > org.apache.oozie.service.CallableQueueService,
> > > > > org.apache.oozie.service.UUIDService,
> > > > > org.apache.oozie.service.ELService,
> > > > > org.apache.oozie.service.AuthorizationService,
> > > > > org.apache.oozie.service.MemoryLocksService,
> > > > > org.apache.oozie.service.DagXLogInfoService,
> > > > > org.apache.oozie.service.SchemaService,
> > > > > org.apache.oozie.service.LiteWorkflowAppService,
> > > > > org.apache.oozie.service.StoreService,
> > > > > org.apache.oozie.service.CoordinatorStoreService,
> > > > > org.apache.oozie.service.SLAStoreService,
> > > > > org.apache.oozie.service.DBLiteWorkflowStoreService,
> > > > > org.apache.oozie.service.CallbackService,
> > > > > org.apache.oozie.service.ActionService,
> > > > > org.apache.oozie.service.ActionCheckerService,
> > > > > org.apache.oozie.service.RecoveryService,
> > > > > org.apache.oozie.service.PurgeService,
> > > > > org.apache.oozie.service.CoordinatorEngineService,
> > > > > org.apache.oozie.service.DagEngineService,
> > > > > org.apache.oozie.service.CoordJobMatLookupTriggerService,
> > > > > org.apache.oozie.service.HadoopAccessorService
> > > > > </value>
> > > > > <description>
> > > > > All services to be created and managed by Oozie Services singleton.
> > > > > Class names must be separated by commas.
> > > > > </description>
> > > > > </property>
> > > > >
> > > > > if I take out org.apache.oozie.service.HadoopAccessorService, then I
> > will
> > > > get
> > > > > 2011-08-23 16:09:45,587 ERROR V1JobsServlet:522 - USER[felix]
> > > > GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
> > > > http://localhost:11000/oozie/v1/jobs?jobtype=pig] error, null
> > > > > java.lang.NullPointerException
> > > > > at
> > > >
> > org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:283)
> > > > > at
> > > >
> > org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:171)
> > > > > at
> > > >
> > org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> > > > > at
> > > >
> > org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> > > > > at
> > > >
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> > > > > at
> > > >
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> > > > > at
> > org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> > > > > at
> > > >
> > com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:371)
> > > > > at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> > > > > at
> > > >
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> > > > > at
> > > >
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> > > > > at
> > > >
> > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> > > > > at
> > > >
> > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> > > > > at
> > > >
> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> > > > > at
> > > >
> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> > > > > at
> > > >
> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> > > > > at
> > > >
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> > > > > at
> > > >
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> > > > > at
> > > >
> > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> > > > > at
> > > > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> > > > > at java.lang.Thread.run(Thread.java:619)
> > > > >
> > > > > your help is appreciated.
> > > > >
> > > > > Felix
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>




------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
   http://groups.yahoo.com/group/Oozie-users/

<*> Your email settings:
   Individual Email | Traditional

<*> To change settings online go to:
   http://groups.yahoo.com/group/Oozie-users/join
   (Yahoo! ID required)

<*> To change settings via email:
   Oozie-users-digest@yahoogroups.com
   Oozie-users-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
   Oozie-users-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
   http://docs.yahoo.com/info/terms/



#2028 From: "Felix" <felixgao@...>
Date: Wed Aug 24, 2011 7:27 pm
Subject: Re: Oozie error when submitting jobs
felixgao
Send Email Send Email
 
hadoop version
Hadoop 0.20.2+228
Subversion  -r cfc3233ece0769b11af9add328261295aaf4d1ad
Compiled by root on Mon Mar 22 03:11:39 EDT 2010

oozie version
Oozie client build version: 2.3.0-cdh3u1

oozie is running as oozie
oozie    26991     1  0 13:57 ?        00:00:07 /usr/bin/java
-Djava.util.logging.config.file=/var/lib/oozie/oozie-server/conf/logging.propert\
ies -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Dderby.stream.error.file=/var/log/oozie/derby.log
-Doozie.home.dir=/usr/lib/oozie -Doozie.config.dir=/etc/oozie
-Doozie.log.dir=/var/log/oozie -Doozie.data.dir=/var/lib/oozie
-Doozie.config.file=oozie-site.xml -Doozie.log4j.file=oozie-log4j.properties
-Doozie.log4j.reload=10 -Doozie.http.hostname=sumo.chi.bluekai.com
-Doozie.http.port=11000 -Doozie.base.url=http://localhost:11000/oozie
-Djava.endorsed.dirs=/usr/lib/oozie/oozie-server/endorsed -classpath
/usr/lib/oozie/oozie-server/bin/bootstrap.jar
-Dcatalina.base=/var/lib/oozie/oozie-server
-Dcatalina.home=/usr/lib/oozie/oozie-server -Djava.io.tmpdir=/var/tmp/oozie
org.apache.catalina.startup.Bootstrap start

OS is centos 5.5 2.6.18-164.15.1.el5 #1 SMP Wed Mar 17 11:30:06 EDT 2010 x86_64
x86_64 x86_64 GNU/Linux

There isn't any entry in proxyuser at the core-site.xml

Felix



--- In Oozie-users@yahoogroups.com, Alejandro Abdelnur <tucu@...> wrote:
>
> Felix,
>
> [Again, moving to the cdh-user@ alias, BCCing oozie-users]
>
> What are the exact versions of Hadoop and Oozie you are using?
>
> What unix user is running Oozie server?
>
> How are you starting Oozier server?
>
> Can you send the configuration of your Hadoop core-site.xml? I just care
> about the properties that have 'proxyuser' in their name.
>
> Thanks.
>
> Alejandro
>
> On Wed, Aug 24, 2011 at 12:01 PM, Felix <felixgao@...> wrote:
>
> > When reverted to the stock oozie-site.xml except I have changed the
> > database to use mysql instead of derby. I still have the exception below.
> >
> > 2011-08-24 13:58:40,107  WARN V1JobsServlet:528 - USER[felix] GROUP[users]
> > TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
> > http://localhost:11000/oozie/v1/jobs?jobtype=pig] error[E0902], E0902:
> > Exception occured: [java.io.IOException: Call to
> > namenode.xxx/69.xxx.xxx.xxx:50001 failed on local exception:
> > java.io.EOFException]
> > org.apache.oozie.servlet.XServletException: E0902: Exception occured:
> > [java.io.IOException: Call to namenode.xxx/69.xxx.xxx.xxx:50001 failed on
> > local exception: java.io.EOFException]
> >         at
> >
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:179)
> >        at
> > org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> >        at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> >        at
> > org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> >        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> >        at
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:290)
> >        at
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> >        at
> > org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> >        at
> >
com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.j\
ava:371)
> >        at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> >        at
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:235)
> >        at
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> >        at
> >
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2\
33)
> >        at
> >
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1\
91)
> >        at
> >
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> >        at
> >
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> >        at
> >
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109\
)
> >        at
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> >        at
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> >        at
> >
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Pr\
otocol.java:588)
> >        at
> > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> >        at java.lang.Thread.run(Thread.java:619)
> > Caused by: org.apache.oozie.service.AuthorizationException: E0902:
> > Exception occured: [java.io.IOException: Call to
> > namenode.xxx/69.xxx.xxx.xxx:50001 failed on local exception:
> > java.io.EOFException]
> >         at
> >
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:318)
> >        at
> >
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:171)
> >        ... 21 more
> > Caused by: org.apache.oozie.service.HadoopAccessorException: E0902:
> > Exception occured: [java.io.IOException: Call to
> > namenode.chi.bluekai.com/69.170.130.176:50001 failed on local exception:
> > java.io.EOFException]
> >         at
> >
org.apache.oozie.service.KerberosHadoopAccessorService.createFileSystem(Kerberos\
HadoopAccessorService.java:211)
> >         at
> >
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:283)
> >        ... 22 more
> > Caused by: java.io.IOException: Call to namenode.xxx/69.xxx.xxx.xxx:50001
> > failed on local exception: java.io.EOFException
> >         at org.apache.hadoop.ipc.Client.wrapException(Client.java:1142)
> >        at org.apache.hadoop.ipc.Client.call(Client.java:1110)
> >        at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:226)
> >        at $Proxy22.getProtocolVersion(Unknown Source)
> >        at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:398)
> >        at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:384)
> >        at
> > org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:111)
> >        at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:213)
> >        at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:180)
> >        at
> >
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.ja\
va:89)
> >        at
> > org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1514)
> >        at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:67)
> >        at
> > org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:1548)
> >        at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1530)
> >        at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:228)
> >         at
> >
org.apache.oozie.service.KerberosHadoopAccessorService$3.run(KerberosHadoopAcces\
sorService.java:203)
> >        at
> >
org.apache.oozie.service.KerberosHadoopAccessorService$3.run(KerberosHadoopAcces\
sorService.java:194)
> >        at java.security.AccessController.doPrivileged(Native Method)
> >        at javax.security.auth.Subject.doAs(Subject.java:396)
> >        at
> >
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1\
127)
> >        at
> >
org.apache.oozie.service.KerberosHadoopAccessorService.createFileSystem(Kerberos\
HadoopAccessorService.java:194)
> >         ... 23 more
> > Caused by: java.io.EOFException
> >        at java.io.DataInputStream.readInt(DataInputStream.java:375)
> >        at
> > org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:815)
> >        at org.apache.hadoop.ipc.Client$Connection.run(Client.java:724)
> >
> >
> >
> > --- In Oozie-users@yahoogroups.com, Alejandro Abdelnur <tucu@> wrote:
> > >
> > > Felix,
> > >
> > > [moving from oozie-users@  (in BCC) to cdh-user@ alias as this seems a
> > CDH
> > > setup  problem]
> > >
> > > If you are using RPM CDH Hadoop and Oozie, you don't have to modify the
> > > HadoopAccessorService.
> > >
> > > Everything should work out of the box with zero configuration.
> > >
> > > Would you try to revert to a clean install and see if you have issues
> > there?
> > >
> > > Thxs.
> > >
> > > Alejandro
> > >
> > >
> > >
> > > On Wed, Aug 24, 2011 at 11:15 AM, Felix <felixgao@> wrote:
> > >
> > > > Alejandro,
> > > >
> > > > I am modifying the oozie.services to
> > > > <property>
> > > >        <name>oozie.services</name>
> > > >        <value>
> > > >            org.apache.oozie.service.SchedulerService,
> > > >            org.apache.oozie.service.InstrumentationService,
> > > >            org.apache.oozie.service.CallableQueueService,
> > > >            org.apache.oozie.service.UUIDService,
> > > >            org.apache.oozie.service.ELService,
> > > >            org.apache.oozie.service.AuthorizationService,
> > > >            org.apache.oozie.service.MemoryLocksService,
> > > >            org.apache.oozie.service.DagXLogInfoService,
> > > >            org.apache.oozie.service.SchemaService,
> > > >            org.apache.oozie.service.LiteWorkflowAppService,
> > > >            org.apache.oozie.service.StoreService,
> > > >            org.apache.oozie.service.CoordinatorStoreService,
> > > >            org.apache.oozie.service.SLAStoreService,
> > > >            org.apache.oozie.service.DBLiteWorkflowStoreService,
> > > >            org.apache.oozie.service.CallbackService,
> > > >            org.apache.oozie.service.ActionService,
> > > >            org.apache.oozie.service.ActionCheckerService,
> > > >            org.apache.oozie.service.RecoveryService,
> > > >            org.apache.oozie.service.PurgeService,
> > > >            org.apache.oozie.service.CoordinatorEngineService,
> > > >            org.apache.oozie.service.DagEngineService,
> > > >            org.apache.oozie.service.CoordJobMatLookupTriggerService,
> > > >            org.apache.oozie.service.HadoopAccessorService
> > > >        </value>
> > > >        <description>
> > > >            All services to be created and managed by Oozie Services
> > > > singleton.
> > > >            Class names must be separated by commas.
> > > >        </description>
> > > >    </property>
> > > >
> > > > because I am seeing E0902: Exception occured:  so
> > > > https://github.com/yahoo/oozie/wiki/FAQ told me to add those to the
> > xml
> > > > file.
> > > >
> > > > --- In Oozie-users@yahoogroups.com, Alejandro Abdelnur <tucu@> wrote:
> > > > >
> > > > > Felix,
> > > > >
> > > > > What are doing that you need to modify the service classes?
> > > > >
> > > > > Thanks.
> > > > >
> > > > > Alejandro
> > > > >
> > > > > On Wed, Aug 24, 2011 at 9:53 AM, Felix <felixgao@> wrote:
> > > > >
> > > > > > NN is running on a different box and so is JT. I do have access to
> > NN
> > > > and
> > > > > > JT from localhost, the box that is used for oozie used to be the
> > > > launchpad
> > > > > > for all of our pig jobs.  When I do hadoop fs I will be able to
> > view
> > > > the
> > > > > > HDFS for which ever user that I am logged in with.
> > > > > >
> > > > > > For my test pig I only have the following in the HDFS
> > > > > > hadoop fs -ls /user/felix/oozie/workflows/test_pig
> > > > > > Found 2 items
> > > > > > -rw-r--r--   2 felix supergroup        367 2011-08-23 14:28
> > > > > > /user/felix/oozie/workflows/test_pig/config-default.xml
> > > > > > drwxr-xr-x   - felix supergroup          0 2011-08-23 14:08
> > > > > > /user/felix/oozie/workflows/test_pig/lib
> > > > > >
> > > > > >
> > > > > > The lib is empty right now.
> > > > > > In my local directory I have
> > > > > > ls -al
> > > > > > total 28
> > > > > > drwxrwxr-x 2 felix felix 4096 Aug 23 16:14 .
> > > > > > drwxrwxr-x 3 felix felix 4096 Aug 23 13:07 ..
> > > > > > -rw-rw-r-- 1 felix felix  367 Aug 23 14:28 config-default.xml
> > > > > > -rw-rw-r-- 1 felix felix  486 Aug 23 15:56 job.properties
> > > > > > -rw-rw-r-- 1 felix felix  309 Aug 23 15:02 pigexample.pig
> > > > > > -rw-rw-r-- 1 felix felix 1190 Aug 23 15:41 pig-wf.xml
> > > > > > -rwxrwxrwx 1 felix felix  929 Aug 23 16:09 submit.sh
> > > > > >
> > > > > >  cat job.properties
> > > > > > #The following attributes must be set
> > > > > > fs.default.name=hdfs://namenode.xxx.xxx:50001
> > > > > > mapred.job.tracker=jobtracker.xxx.xxx:50002
> > > > > > oozie.use.system.libpath=true
> > > > > >
> > oozie.libpath=hdfs://namenode.xxx.xxx:50001/user/oozie/share/pig/lib/
> > > > > > queueName=default
> > > > > > #additional
> > > > > >
> > > > > >
> > > >
> >
oozie.wf.application.path=hdfs://namenode.xxx.xxx:50001/user/felix/oozie/workflo\
ws/test_pig
> > > > > > inputDir=/user/felix/test_input.data
> > > > > > outputDir=/user/felix/oozie_output/pig_test
> > > > > >
> > > > > > I submitted the job to Oozie using
> > > > > > oozie pig -oozie http://localhost:11000/oozie -file pigexample.pig
> > > > -config
> > > > > > job.properties
> > > > > >
> > > > > > hadoop we are using is 0.20.2 and oozie we are using is 2.3.0. Both
> > are
> > > > > > from cloudera's RPM.
> > > > > >
> > > > > > I hope this is clear enough.
> > > > > >
> > > > > > --- In Oozie-users@yahoogroups.com, Mohammad Islam <mislam77@>
> > wrote:
> > > > > > >
> > > > > > > Do you have the NN running on the same box?
> > > > > > >
> > > > > > > If not,  do you have the access from the localhost to NN? Did
> > you
> > > > able
> > > > > > to run "haddop fs ..." command from the localhost?
> > > > > > >
> > > > > > >
> > > > > > > Which version of hadoop and what version of oozie you are using?
> > > > > > > What is the wf apppath in job.properties?
> > > > > > >
> > > > > > > Regards,
> > > > > > > Mohammad
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: Felix <felixgao@>
> > > > > > > To: Oozie-users@yahoogroups.com
> > > > > > > Sent: Tuesday, August 23, 2011 3:28 PM
> > > > > > > Subject: [Oozie-users] Oozie error when submitting jobs
> > > > > > >
> > > > > > >
> > > > > > > Â
> > > > > > > Hi all I have a simple pig job for testing that I would like to
> > use
> > > > oozie
> > > > > > to manage.  When I do the following I got
> > > > > > >
> > > > > > > oozie pig -oozie http://localhost:11000/oozie -file
> > pigexample.pig
> > > > > > -config job.properties
> > > > > > > Error: E0902 : E0902: Exception occured: [java.io.IOException:
> > Call
> > > > to
> > > > > > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > > > > > java.io.EOFException]
> > > > > > >
> > > > > > > 2011-08-23 17:18:11,861  WARN V1JobsServlet:528 - USER[felix]
> > > > > > GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
> > > > > > http://localhost:11000/oozie/v1/jobs?jobtype=pig] error[E0902],
> > E0902:
> > > > > > Exception occured: [java.io.IOException: Call to
> > > > > > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > > > > > java.io.EOFException]
> > > > > > > org.apache.oozie.servlet.XServletException: E0902: Exception
> > occured:
> > > > > > [java.io.IOException: Call to namenode/69.xxx.xxx.xxx:50001 failed
> > on
> > > > local
> > > > > > exception: java.io.EOFException]
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:179)
> > > > > > > at
> > > > > >
> > > >
> > org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> > > > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> > > > > > > at
> > > > > >
> > > >
> > org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> > > > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:290)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> > > > > > > at
> > > > org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> > > > > > > at
> > > > > >
> > > >
> >
com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.j\
ava:371)
> > > > > > > at
> > org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:235)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2\
33)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1\
91)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109\
)
> > > > > > > at
> > > > > >
> > > >
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> > > > > > > at
> > > > > >
> > > >
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Pr\
otocol.java:588)
> > > > > > > at
> > > > > >
> > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> > > > > > > at java.lang.Thread.run(Thread.java:619)
> > > > > > > Caused by: org.apache.oozie.service.AuthorizationException:
> > E0902:
> > > > > > Exception occured: [java.io.IOException: Call to
> > > > > > namenode/69.xxx.xxx.xxx:50001 failed on local exception:
> > > > > > java.io.EOFException]
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:318)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:171)
> > > > > > > ... 21 more
> > > > > > > Caused by: org.apache.oozie.service.HadoopAccessorException:
> > E0902:
> > > > > > Exception occured: [java.io.IOException: Call to
> > > > > > namenode.chi.bluekai.com/69.170.130.176:50001 failed on local
> > > > exception:
> > > > > > java.io.EOFException]
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorSe\
rvice.java:144)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:283)
> > > > > > > ... 22 more
> > > > > > > Caused by: java.io.IOException: Call to
> > namenode/69.xxx.xxx.xxx:50001
> > > > > > failed on local exception: java.io.EOFException
> > > > > > > at org.apache.hadoop.ipc.Client.wrapException(Client.java:1142)
> > > > > > > at org.apache.hadoop.ipc.Client.call(Client.java:1110)
> > > > > > > at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:226)
> > > > > > > at $Proxy22.getProtocolVersion(Unknown Source)
> > > > > > > at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:398)
> > > > > > > at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:384)
> > > > > > > at
> > > > org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:111)
> > > > > > > at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:213)
> > > > > > > at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:180)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.ja\
va:89)
> > > > > > > at
> > > > org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1514)
> > > > > > > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:67)
> > > > > > > at
> > > > > >
> > org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:1548)
> > > > > > > at
> > org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1530)
> > > > > > > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:228)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorSe\
rvice.java:141)
> > > > > > > ... 23 more
> > > > > > > Caused by: java.io.EOFException
> > > > > > > at java.io.DataInputStream.readInt(DataInputStream.java:375)
> > > > > > > at
> > > > > >
> > > >
> > org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:815)
> > > > > > > at org.apache.hadoop.ipc.Client$Connection.run(Client.java:724)
> > > > > > >
> > > > > > > in my oozie-site.xml I have the following services
> > > > > > > <property>
> > > > > > > <name>oozie.services</name>
> > > > > > > <value>
> > > > > > > org.apache.oozie.service.SchedulerService,
> > > > > > > org.apache.oozie.service.InstrumentationService,
> > > > > > > org.apache.oozie.service.CallableQueueService,
> > > > > > > org.apache.oozie.service.UUIDService,
> > > > > > > org.apache.oozie.service.ELService,
> > > > > > > org.apache.oozie.service.AuthorizationService,
> > > > > > > org.apache.oozie.service.MemoryLocksService,
> > > > > > > org.apache.oozie.service.DagXLogInfoService,
> > > > > > > org.apache.oozie.service.SchemaService,
> > > > > > > org.apache.oozie.service.LiteWorkflowAppService,
> > > > > > > org.apache.oozie.service.StoreService,
> > > > > > > org.apache.oozie.service.CoordinatorStoreService,
> > > > > > > org.apache.oozie.service.SLAStoreService,
> > > > > > > org.apache.oozie.service.DBLiteWorkflowStoreService,
> > > > > > > org.apache.oozie.service.CallbackService,
> > > > > > > org.apache.oozie.service.ActionService,
> > > > > > > org.apache.oozie.service.ActionCheckerService,
> > > > > > > org.apache.oozie.service.RecoveryService,
> > > > > > > org.apache.oozie.service.PurgeService,
> > > > > > > org.apache.oozie.service.CoordinatorEngineService,
> > > > > > > org.apache.oozie.service.DagEngineService,
> > > > > > > org.apache.oozie.service.CoordJobMatLookupTriggerService,
> > > > > > > org.apache.oozie.service.HadoopAccessorService
> > > > > > > </value>
> > > > > > > <description>
> > > > > > > All services to be created and managed by Oozie Services
> > singleton.
> > > > > > > Class names must be separated by commas.
> > > > > > > </description>
> > > > > > > </property>
> > > > > > >
> > > > > > > if I take out org.apache.oozie.service.HadoopAccessorService,
> > then I
> > > > will
> > > > > > get
> > > > > > > 2011-08-23 16:09:45,587 ERROR V1JobsServlet:522 - USER[felix]
> > > > > > GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
> > > > > > http://localhost:11000/oozie/v1/jobs?jobtype=pig] error, null
> > > > > > > java.lang.NullPointerException
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:283)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:171)
> > > > > > > at
> > > > > >
> > > >
> > org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
> > > > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> > > > > > > at
> > > > > >
> > > >
> > org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
> > > > > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:290)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> > > > > > > at
> > > > org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
> > > > > > > at
> > > > > >
> > > >
> >
com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.j\
ava:371)
> > > > > > > at
> > org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:235)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2\
33)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1\
91)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109\
)
> > > > > > > at
> > > > > >
> > > >
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> > > > > > > at
> > > > > >
> > > >
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> > > > > > > at
> > > > > >
> > > >
> >
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Pr\
otocol.java:588)
> > > > > > > at
> > > > > >
> > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> > > > > > > at java.lang.Thread.run(Thread.java:619)
> > > > > > >
> > > > > > > your help is appreciated.
> > > > > > >
> > > > > > > Felix
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ------------------------------------
> > > > > >
> > > > > > Yahoo! Groups Links
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>

#2029 From: Mohammad Islam <mislam77@...>
Date: Wed Aug 24, 2011 8:21 pm
Subject: Re: Hive action [WAS: GH Oozie pullrequests]
mislam77@...
Send Email Send Email
 


>In the mean time, as a temporary solution, we can do the same thing we do for Hadoop, we consume the artifacts from an alternate repository.  This is my interim >solution for getting Hive into Apache Oozie as soon as possible. Later, when Hive publishes correct artifacts to Apache Maven repo, we'll just update the version and >we'll be done.

Hi Alejandro,
It was my bad that the yahoo dependency of hadoop to build was not taken off yet.
Do you see any issue of using apache maven repository for hadoop?
I will take that an action item soon and will create a JIRA.

Regards,
Mohammad




On Wed, Aug 24, 2011 at 1:39 AM, Andreas Neumann <anew@...> wrote:


Alejandro,

Ideally we would want to depend only on Apache. Given that Apache Hive is already attempting to provide mavenized builds, would it be possible for you to help them do it correctly?

Thanks 
andreas
neumann
grid architect
 
anew@...
408-336-0945
 
701 first avenue, sunnyvale, ca, 94089-0703, us
phone (408) 349 3300    fax (408) 349 3301
 

 

From: Alejandro Abdelnur <tucu@...>
Reply-To: "Oozie-users@yahoogroups.com" <Oozie-users@yahoogroups.com>
Date: Tue, 23 Aug 2011 13:03:44 -0700
To: "Oozie-users@yahoogroups.com" <Oozie-users@yahoogroups.com>
Subject: Re: [Oozie-users] Hive action [WAS: GH Oozie pullrequests]

 
Mohammad,

Hive creates a valid POM, it is just incorrect, it does not have all the required dependencies to work.

BTW, this is something it should be discussed in the apache alias (when are we switching?) and decided by the community.

Thanks.

Alejandro

On Tue, Aug 23, 2011 at 12:49 PM, Mohammad Islam <mislam77@...> wrote:


Hi Alejandro,
I will run through the proposal to our team of using CDH maven repo.

One question that will surely come: why the current hive maven can't be utilized.
According to the JIRA, it was mavenized.
Is it they use non-standard way and we are expecting in a standard way?

Or is it there artifacts are not workable/usable at all?

Is it a lot of work for hive team to achieve this through Apache Hive?

Does Sqoop experience the same issue?
Regards,
Mohammad

From: Alejandro Abdelnur <tucu@...>
To: Oozie-users@yahoogroups.com
Sent: Tuesday, August 23, 2011 10:52 AM
Subject: [Oozie-users] Hive action [WAS: GH Oozie pullrequests]

 
Following up on this, 

I really want to get Hive & Sqoop actions into Oozie.

Our roadblock is the unavailability of proper Hive POMs in Apache Maven Repo.

I would like to insist once more in the temporary workaround of using CDH Hive which is available in Cloudera Maven Repo.

We are already doing that for Hadoop JARs which are coming from the 'GH yahoo' Maven repo.

Again, this is a temporary solution until Hive solves this issue.

Thoughts?

Alejandro

On Tue, Aug 23, 2011 at 6:32 AM, Alejandro Abdelnur <tucu@...> wrote:
Hi Mohammad,

At this point  somebody has to address HIVE-2391 and have a Hive release with such patch. 

Then Apache Hive will be usable as a Maven artifact for us.

I'm not sure how high priority is for them to fix this. I assume low.

Apache Hive uses Ant & Ivy for their build system. For CDH Hive we reverse engineer the POMs and use a Maven-Ant build environment to deploy them. The CDH Hive build environment was a stop gap solution for us, we really want Apache Hive to produce the POM. 

The CDH Hive POM dependencies work but Ant&Ivy configuration and POM generation is anything but an obscure thing to me. 

The good thing is that we know that the CDH POMs dependencies are the end goal.

If you guys have people working in Hive it would be great if you can push them for this, I'll do the same with out folks.

Else, we could use CDH Hive as temporary solution.

Thoughts?

Thanks.

Alejandro

On Tue, Aug 23, 2011 at 12:36 AM, Mohammad Islam <mislam77@...> wrote:


Hi Alejandro,

Is there any works in progress to address the hive artifacts issue?
More specifically, what is the problem? If you can elaborate, I can follow up. 

Is there any acceptable workaround?

Do you think using the JIRA (that was created for hive artifacts - that I sent) might be a way to express the missing pieces?

Do you have any suggestion?

btw, most of PRs are taken care of.

Regards,
Mohammad


From: Alejandro Abdelnur <tucu@...>
To: Oozie-users@yahoogroups.com
Sent: Monday, August 22, 2011 1:00 PM
Subject: Re: [Oozie-users] GH Oozie pullrequests

 
Mohammad,

Thanks.

Regarding Hive, as I've mentioned before, Hive JARs in Apache Maven repo are not usable (https://issues.apache.org/jira/browse/HIVE-2391). Until this is fixed I don't see a way of using Apache Hive artifacts. If you have an idea, please let let me know.

There is also a PR from Roman, I've asked him to backported to 2.3 as well.

Thanks.

Alejandro

On Mon, Aug 22, 2011 at 12:56 PM, Mohammad Islam <mislam77@...> wrote:


Hi Alejandor,
I'm going to push couple of of yours.
What about Hive action?

I will also push some others too.

There are few that needs more discussion.

Regards,
Mohammad



From: Alejandro Abdelnur <tucu@...>
To: oozie-users <Oozie-users@yahoogroups.com>
Sent: Monday, August 22, 2011 12:49 PM
Subject: [Oozie-users] GH Oozie pullrequests

 
Currently we have 16 pull requests open in GH yahoo/oozie.

Is anybody looking at integrating them?

Thanks.

Alejandro






















#2030 From: Frank Astier <fastier@...>
Date: Wed Aug 24, 2011 8:24 pm
Subject: Maven repository?
fastier
Send Email Send Email
 
Hi -

Is there a way to include a dependency on a repository for oozie 3.0.2? It looks
like the project on github doesn't have a "version" that maven dependency is
expecting. I need to compile a project using maven and oozie/client.

PS: I'm pretty new at maven.

Frank
Frank
fastier@...

#2031 From: Alejandro Abdelnur <tucu@...>
Date: Wed Aug 24, 2011 8:53 pm
Subject: Re: Hive action [WAS: GH Oozie pullrequests]
tucu0
Send Email Send Email
 
Mohammad, 

Nobody's bad. We need to use Hadoop JARs with security from a release that works for people to be able to use it.

Personally I'm good depending on Y's Hadoop JARs till there is an alternative.

Thxs.

Alejandro

On Wed, Aug 24, 2011 at 1:21 PM, Mohammad Islam <mislam77@...> wrote:




>In the mean time, as a temporary solution, we can do the same thing we do for Hadoop, we consume the artifacts from an alternate repository.  This is my interim >solution for getting Hive into Apache Oozie as soon as possible. Later, when Hive publishes correct artifacts to Apache Maven repo, we'll just update the version and >we'll be done.

Hi Alejandro,
It was my bad that the yahoo dependency of hadoop to build was not taken off yet.
Do you see any issue of using apache maven repository for hadoop?
I will take that an action item soon and will create a JIRA.

Regards,
Mohammad




On Wed, Aug 24, 2011 at 1:39 AM, Andreas Neumann <anew@...> wrote:


Alejandro,

Ideally we would want to depend only on Apache. Given that Apache Hive is already attempting to provide mavenized builds, would it be possible for you to help them do it correctly?

Thanks 
andreas
neumann
grid architect
 
anew@...
408-336-0945
 
701 first avenue, sunnyvale, ca, 94089-0703, us
phone (408) 349 3300    fax (408) 349 3301
 

 

From: Alejandro Abdelnur <tucu@...>
Reply-To: "Oozie-users@yahoogroups.com" <Oozie-users@yahoogroups.com>
Date: Tue, 23 Aug 2011 13:03:44 -0700
To: "Oozie-users@yahoogroups.com" <Oozie-users@yahoogroups.com>
Subject: Re: [Oozie-users] Hive action [WAS: GH Oozie pullrequests]

 
Mohammad,

Hive creates a valid POM, it is just incorrect, it does not have all the required dependencies to work.

BTW, this is something it should be discussed in the apache alias (when are we switching?) and decided by the community.

Thanks.

Alejandro

On Tue, Aug 23, 2011 at 12:49 PM, Mohammad Islam <mislam77@...> wrote:


Hi Alejandro,
I will run through the proposal to our team of using CDH maven repo.

One question that will surely come: why the current hive maven can't be utilized.
According to the JIRA, it was mavenized.
Is it they use non-standard way and we are expecting in a standard way?

Or is it there artifacts are not workable/usable at all?

Is it a lot of work for hive team to achieve this through Apache Hive?

Does Sqoop experience the same issue?
Regards,
Mohammad

From: Alejandro Abdelnur <tucu@...>
To: Oozie-users@yahoogroups.com
Sent: Tuesday, August 23, 2011 10:52 AM
Subject: [Oozie-users] Hive action [WAS: GH Oozie pullrequests]

 
Following up on this, 

I really want to get Hive & Sqoop actions into Oozie.

Our roadblock is the unavailability of proper Hive POMs in Apache Maven Repo.

I would like to insist once more in the temporary workaround of using CDH Hive which is available in Cloudera Maven Repo.

We are already doing that for Hadoop JARs which are coming from the 'GH yahoo' Maven repo.

Again, this is a temporary solution until Hive solves this issue.

Thoughts?

Alejandro

On Tue, Aug 23, 2011 at 6:32 AM, Alejandro Abdelnur <tucu@...> wrote:
Hi Mohammad,

At this point  somebody has to address HIVE-2391 and have a Hive release with such patch. 

Then Apache Hive will be usable as a Maven artifact for us.

I'm not sure how high priority is for them to fix this. I assume low.

Apache Hive uses Ant & Ivy for their build system. For CDH Hive we reverse engineer the POMs and use a Maven-Ant build environment to deploy them. The CDH Hive build environment was a stop gap solution for us, we really want Apache Hive to produce the POM. 

The CDH Hive POM dependencies work but Ant&Ivy configuration and POM generation is anything but an obscure thing to me. 

The good thing is that we know that the CDH POMs dependencies are the end goal.

If you guys have people working in Hive it would be great if you can push them for this, I'll do the same with out folks.

Else, we could use CDH Hive as temporary solution.

Thoughts?

Thanks.

Alejandro

On Tue, Aug 23, 2011 at 12:36 AM, Mohammad Islam <mislam77@...> wrote:


Hi Alejandro,

Is there any works in progress to address the hive artifacts issue?
More specifically, what is the problem? If you can elaborate, I can follow up. 

Is there any acceptable workaround?

Do you think using the JIRA (that was created for hive artifacts - that I sent) might be a way to express the missing pieces?

Do you have any suggestion?

btw, most of PRs are taken care of.

Regards,
Mohammad


From: Alejandro Abdelnur <tucu@...>
To: Oozie-users@yahoogroups.com
Sent: Monday, August 22, 2011 1:00 PM
Subject: Re: [Oozie-users] GH Oozie pullrequests

 
Mohammad,

Thanks.

Regarding Hive, as I've mentioned before, Hive JARs in Apache Maven repo are not usable (https://issues.apache.org/jira/browse/HIVE-2391). Until this is fixed I don't see a way of using Apache Hive artifacts. If you have an idea, please let let me know.

There is also a PR from Roman, I've asked him to backported to 2.3 as well.

Thanks.

Alejandro

On Mon, Aug 22, 2011 at 12:56 PM, Mohammad Islam <mislam77@...> wrote:


Hi Alejandor,
I'm going to push couple of of yours.
What about Hive action?

I will also push some others too.

There are few that needs more discussion.

Regards,
Mohammad



From: Alejandro Abdelnur <tucu@...>
To: oozie-users <Oozie-users@yahoogroups.com>
Sent: Monday, August 22, 2011 12:49 PM
Subject: [Oozie-users] GH Oozie pullrequests

 
Currently we have 16 pull requests open in GH yahoo/oozie.

Is anybody looking at integrating them?

Thanks.

Alejandro

























#2032 From: Angelo Kaichen Huang <angeloh@...>
Date: Wed Aug 24, 2011 10:02 pm
Subject: Re: Maven repository?
angelokh...
Send Email Send Email
 
Could you try these?

<dependency>
  <groupId>com.yahoo.oozie</groupId>
  <artifactId>oozie-client</artifactId>
  <version>3.0.0</version>
</dependency>

<dependency>
  <groupId>com.yahoo.oozie</groupId>
  <artifactId>oozie-core</artifactId>
  <version>3.0.0</version>
</dependency>

--angelo

Frank Astier wrote:
 

Hi -

Is there a way to include a dependency on a repository for oozie 3.0.2? It looks like the project on github doesn't have a "version" that maven dependency is expecting. I need to compile a project using maven and oozie/client.

PS: I'm pretty new at maven.

Frank
Frank
fastier@...



#2033 From: Andreas Neumann <anew@...>
Date: Thu Aug 25, 2011 9:29 am
Subject: Re: Hive action [WAS: GH Oozie pullrequests]
neumandreas
Send Email Send Email
 
I don't mind using a different repository – as long as it is temporary and it has the same release as Apache. 
But if it takes little effort to fix Apache Hive then I would rather spend that effort. How much work is it to fix it?

Thanks –Andreas

From: Alejandro Abdelnur <tucu@...>
Reply-To: "Oozie-users@yahoogroups.com" <Oozie-users@yahoogroups.com>
Date: Wed, 24 Aug 2011 13:53:55 -0700
To: "Oozie-users@yahoogroups.com" <Oozie-users@yahoogroups.com>
Subject: Re: [Oozie-users] Hive action [WAS: GH Oozie pullrequests]

 

Mohammad, 


Nobody's bad. We need to use Hadoop JARs with security from a release that works for people to be able to use it.

Personally I'm good depending on Y's Hadoop JARs till there is an alternative.

Thxs.

Alejandro

On Wed, Aug 24, 2011 at 1:21 PM, Mohammad Islam <mislam77@...> wrote:




>In the mean time, as a temporary solution, we can do the same thing we do for Hadoop, we consume the artifacts from an alternate repository.  This is my interim >solution for getting Hive into Apache Oozie as soon as possible. Later, when Hive publishes correct artifacts to Apache Maven repo, we'll just update the version and >we'll be done.

Hi Alejandro,
It was my bad that the yahoo dependency of hadoop to build was not taken off yet.
Do you see any issue of using apache maven repository for hadoop?
I will take that an action item soon and will create a JIRA.

Regards,
Mohammad




On Wed, Aug 24, 2011 at 1:39 AM, Andreas Neumann <anew@...> wrote:


Alejandro,

Ideally we would want to depend only on Apache. Given that Apache Hive is already attempting to provide mavenized builds, would it be possible for you to help them do it correctly?

Thanks 
andreas
neumann
grid architect
 
anew@...
408-336-0945
 
701 first avenue, sunnyvale, ca, 94089-0703, us
phone (408) 349 3300    fax (408) 349 3301
 

 

From: Alejandro Abdelnur <tucu@...>
Reply-To: "Oozie-users@yahoogroups.com" <Oozie-users@yahoogroups.com>
Date: Tue, 23 Aug 2011 13:03:44 -0700
To: "Oozie-users@yahoogroups.com" <Oozie-users@yahoogroups.com>
Subject: Re: [Oozie-users] Hive action [WAS: GH Oozie pullrequests]

 
Mohammad,

Hive creates a valid POM, it is just incorrect, it does not have all the required dependencies to work.

BTW, this is something it should be discussed in the apache alias (when are we switching?) and decided by the community.

Thanks.

Alejandro

On Tue, Aug 23, 2011 at 12:49 PM, Mohammad Islam <mislam77@...> wrote:


Hi Alejandro,
I will run through the proposal to our team of using CDH maven repo.

One question that will surely come: why the current hive maven can't be utilized.
According to the JIRA, it was mavenized.
Is it they use non-standard way and we are expecting in a standard way?

Or is it there artifacts are not workable/usable at all?

Is it a lot of work for hive team to achieve this through Apache Hive?

Does Sqoop experience the same issue?
Regards,
Mohammad

From: Alejandro Abdelnur <tucu@...>
To: Oozie-users@yahoogroups.com
Sent: Tuesday, August 23, 2011 10:52 AM
Subject: [Oozie-users] Hive action [WAS: GH Oozie pullrequests]

 
Following up on this, 

I really want to get Hive & Sqoop actions into Oozie.

Our roadblock is the unavailability of proper Hive POMs in Apache Maven Repo.

I would like to insist once more in the temporary workaround of using CDH Hive which is available in Cloudera Maven Repo.

We are already doing that for Hadoop JARs which are coming from the 'GH yahoo' Maven repo.

Again, this is a temporary solution until Hive solves this issue.

Thoughts?

Alejandro

On Tue, Aug 23, 2011 at 6:32 AM, Alejandro Abdelnur <tucu@...> wrote:
Hi Mohammad,

At this point  somebody has to address HIVE-2391 and have a Hive release with such patch. 

Then Apache Hive will be usable as a Maven artifact for us.

I'm not sure how high priority is for them to fix this. I assume low.

Apache Hive uses Ant & Ivy for their build system. For CDH Hive we reverse engineer the POMs and use a Maven-Ant build environment to deploy them. The CDH Hive build environment was a stop gap solution for us, we really want Apache Hive to produce the POM. 

The CDH Hive POM dependencies work but Ant&Ivy configuration and POM generation is anything but an obscure thing to me. 

The good thing is that we know that the CDH POMs dependencies are the end goal.

If you guys have people working in Hive it would be great if you can push them for this, I'll do the same with out folks.

Else, we could use CDH Hive as temporary solution.

Thoughts?

Thanks.

Alejandro

On Tue, Aug 23, 2011 at 12:36 AM, Mohammad Islam <mislam77@...> wrote:


Hi Alejandro,

Is there any works in progress to address the hive artifacts issue?
More specifically, what is the problem? If you can elaborate, I can follow up. 

Is there any acceptable workaround?

Do you think using the JIRA (that was created for hive artifacts - that I sent) might be a way to express the missing pieces?

Do you have any suggestion?

btw, most of PRs are taken care of.

Regards,
Mohammad


From: Alejandro Abdelnur <tucu@...>
To: Oozie-users@yahoogroups.com
Sent: Monday, August 22, 2011 1:00 PM
Subject: Re: [Oozie-users] GH Oozie pullrequests

 
Mohammad,

Thanks.

Regarding Hive, as I've mentioned before, Hive JARs in Apache Maven repo are not usable (https://issues.apache.org/jira/browse/HIVE-2391). Until this is fixed I don't see a way of using Apache Hive artifacts. If you have an idea, please let let me know.

There is also a PR from Roman, I've asked him to backported to 2.3 as well.

Thanks.

Alejandro

On Mon, Aug 22, 2011 at 12:56 PM, Mohammad Islam <mislam77@...> wrote:


Hi Alejandor,
I'm going to push couple of of yours.
What about Hive action?

I will also push some others too.

There are few that needs more discussion.

Regards,
Mohammad



From: Alejandro Abdelnur <tucu@...>
To: oozie-users <Oozie-users@yahoogroups.com>
Sent: Monday, August 22, 2011 12:49 PM
Subject: [Oozie-users] GH Oozie pullrequests

 
Currently we have 16 pull requests open in GH yahoo/oozie.

Is anybody looking at integrating them?

Thanks.

Alejandro

























#2034 From: Alejandro Abdelnur <tucu@...>
Date: Thu Aug 25, 2011 1:33 pm
Subject: Re: Hive action [WAS: GH Oozie pullrequests]
tucu0
Send Email Send Email
 
Hi Andreas,

Yes, definitely would be temporary, same was with Hadoop security, until we have Apache viable alternatives.

Hive build system is based on Ant & Ivy and generates something like 10 JARs, some used, some not. At the moment the POMs have invalid dependencies. I believe they use some ivy functionality to create them based on the ivy dependencies. How much work to fix it? I've tried once to tackle that and I've failed, a the end we crafted the POMs by Hand parameterizing the dependencies versions. 

Thanks, I'll start updating the Hive patch for Oozie then.

Alejandro


On Thu, Aug 25, 2011 at 2:29 AM, Andreas Neumann <anew@...> wrote:


I don't mind using a different repository – as long as it is temporary and it has the same release as Apache. 
But if it takes little effort to fix Apache Hive then I would rather spend that effort. How much work is it to fix it?

Thanks –Andreas

From: Alejandro Abdelnur <tucu@...>
Reply-To: "Oozie-users@yahoogroups.com" <Oozie-users@yahoogroups.com>
Date: Wed, 24 Aug 2011 13:53:55 -0700

To: "Oozie-users@yahoogroups.com" <Oozie-users@yahoogroups.com>
Subject: Re: [Oozie-users] Hive action [WAS: GH Oozie pullrequests]

 

Mohammad, 


Nobody's bad. We need to use Hadoop JARs with security from a release that works for people to be able to use it.

Personally I'm good depending on Y's Hadoop JARs till there is an alternative.

Thxs.

Alejandro

On Wed, Aug 24, 2011 at 1:21 PM, Mohammad Islam <mislam77@...> wrote:




>In the mean time, as a temporary solution, we can do the same thing we do for Hadoop, we consume the artifacts from an alternate repository.  This is my interim >solution for getting Hive into Apache Oozie as soon as possible. Later, when Hive publishes correct artifacts to Apache Maven repo, we'll just update the version and >we'll be done.

Hi Alejandro,
It was my bad that the yahoo dependency of hadoop to build was not taken off yet.
Do you see any issue of using apache maven repository for hadoop?
I will take that an action item soon and will create a JIRA.

Regards,
Mohammad




On Wed, Aug 24, 2011 at 1:39 AM, Andreas Neumann <anew@...> wrote:


Alejandro,

Ideally we would want to depend only on Apache. Given that Apache Hive is already attempting to provide mavenized builds, would it be possible for you to help them do it correctly?

Thanks 
andreas
neumann
grid architect
 
anew@...
408-336-0945
 
701 first avenue, sunnyvale, ca, 94089-0703, us
phone (408) 349 3300    fax (408) 349 3301
 

 

From: Alejandro Abdelnur <tucu@...>
Reply-To: "Oozie-users@yahoogroups.com" <Oozie-users@yahoogroups.com>
Date: Tue, 23 Aug 2011 13:03:44 -0700
To: "Oozie-users@yahoogroups.com" <Oozie-users@yahoogroups.com>
Subject: Re: [Oozie-users] Hive action [WAS: GH Oozie pullrequests]

 
Mohammad,

Hive creates a valid POM, it is just incorrect, it does not have all the required dependencies to work.

BTW, this is something it should be discussed in the apache alias (when are we switching?) and decided by the community.

Thanks.

Alejandro

On Tue, Aug 23, 2011 at 12:49 PM, Mohammad Islam <mislam77@...> wrote:


Hi Alejandro,
I will run through the proposal to our team of using CDH maven repo.

One question that will surely come: why the current hive maven can't be utilized.
According to the JIRA, it was mavenized.
Is it they use non-standard way and we are expecting in a standard way?

Or is it there artifacts are not workable/usable at all?

Is it a lot of work for hive team to achieve this through Apache Hive?

Does Sqoop experience the same issue?
Regards,
Mohammad

From: Alejandro Abdelnur <tucu@...>
To: Oozie-users@yahoogroups.com
Sent: Tuesday, August 23, 2011 10:52 AM
Subject: [Oozie-users] Hive action [WAS: GH Oozie pullrequests]

 
Following up on this, 

I really want to get Hive & Sqoop actions into Oozie.

Our roadblock is the unavailability of proper Hive POMs in Apache Maven Repo.

I would like to insist once more in the temporary workaround of using CDH Hive which is available in Cloudera Maven Repo.

We are already doing that for Hadoop JARs which are coming from the 'GH yahoo' Maven repo.

Again, this is a temporary solution until Hive solves this issue.

Thoughts?

Alejandro

On Tue, Aug 23, 2011 at 6:32 AM, Alejandro Abdelnur <tucu@...> wrote:
Hi Mohammad,

At this point  somebody has to address HIVE-2391 and have a Hive release with such patch. 

Then Apache Hive will be usable as a Maven artifact for us.

I'm not sure how high priority is for them to fix this. I assume low.

Apache Hive uses Ant & Ivy for their build system. For CDH Hive we reverse engineer the POMs and use a Maven-Ant build environment to deploy them. The CDH Hive build environment was a stop gap solution for us, we really want Apache Hive to produce the POM. 

The CDH Hive POM dependencies work but Ant&Ivy configuration and POM generation is anything but an obscure thing to me. 

The good thing is that we know that the CDH POMs dependencies are the end goal.

If you guys have people working in Hive it would be great if you can push them for this, I'll do the same with out folks.

Else, we could use CDH Hive as temporary solution.

Thoughts?

Thanks.

Alejandro

On Tue, Aug 23, 2011 at 12:36 AM, Mohammad Islam <mislam77@...> wrote:


Hi Alejandro,

Is there any works in progress to address the hive artifacts issue?
More specifically, what is the problem? If you can elaborate, I can follow up. 

Is there any acceptable workaround?

Do you think using the JIRA (that was created for hive artifacts - that I sent) might be a way to express the missing pieces?

Do you have any suggestion?

btw, most of PRs are taken care of.

Regards,
Mohammad


From: Alejandro Abdelnur <tucu@...>
To: Oozie-users@yahoogroups.com
Sent: Monday, August 22, 2011 1:00 PM
Subject: Re: [Oozie-users] GH Oozie pullrequests

 
Mohammad,

Thanks.

Regarding Hive, as I've mentioned before, Hive JARs in Apache Maven repo are not usable (https://issues.apache.org/jira/browse/HIVE-2391). Until this is fixed I don't see a way of using Apache Hive artifacts. If you have an idea, please let let me know.

There is also a PR from Roman, I've asked him to backported to 2.3 as well.

Thanks.

Alejandro

On Mon, Aug 22, 2011 at 12:56 PM, Mohammad Islam <mislam77@...> wrote:


Hi Alejandor,
I'm going to push couple of of yours.
What about Hive action?

I will also push some others too.

There are few that needs more discussion.

Regards,
Mohammad



From: Alejandro Abdelnur <tucu@...>
To: oozie-users <Oozie-users@yahoogroups.com>
Sent: Monday, August 22, 2011 12:49 PM
Subject: [Oozie-users] GH Oozie pullrequests

 
Currently we have 16 pull requests open in GH yahoo/oozie.

Is anybody looking at integrating them?

Thanks.

Alejandro




























#2035 From: "vishal.santoshi" <vishal.santoshi@...>
Date: Thu Aug 25, 2011 1:51 pm
Subject: timeout in controls
vishal.santoshi
Send Email Send Email
 
According to Coordinator specification timeout's default value is -1

timeout: The maximum time, in minutes, that a materialized action will be
waiting for the additional conditions to be satisfied before being discarded. A
timeout of 0 indicates that at the time of materialization all the other
conditions must be satisfied, else the action will be discarded. A timeout of 0
indicates that if all the input events are not satisfied at the time of action
materizlization, the action should timeout immediately. A timeout of -1
indicates no timeout, the materialized action will wait forever for the other
conditions to be satisfied. The default value is -1 .




I have a


  <controls>
         <concurrency>1</concurrency>
         <execution>FIFO</execution>
  </controls>


And thus would assume no timepout. It has to wait indefinitely for data in 's to
appear.

Is there any other reason my job is TIMEDOUT ? Note that it does execute when
all data is available.

Regards.

#2036 From: "Felix" <felixgao@...>
Date: Thu Aug 25, 2011 5:19 pm
Subject: Re: Oozie error when submitting jobs
felixgao
Send Email Send Email
 
I have added
  <property>
    	 <name>hadoop.proxyuser.oozie.hosts</name>
   	  <value>*</value>
      </property>
      <property>
     	 <name>hadoop.proxyuser.oozie.groups</name>
     	 <value>*</value>
      </property>

to the core-site.xml on namenode.   After restart namenode,  I still see the
following exceptions.

2011-08-25 11:46:09,477  WARN V1JobsServlet:528 - USER[felix] GROUP[users]
TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST
http://localhost:11000/oozie/v1/jobs?jobtype=pig] error[E0902], E0902: Exception
occured: [java.io.IOException: Call to
namenode.xxx.xxx.com/xxx.xxx.xxx.xxx:50001 failed on local exception:
java.io.EOFException]
org.apache.oozie.servlet.XServletException: E0902: Exception occured:
[java.io.IOException: Call to namenode.xxx.xxx.com/xxx.xxx.xxx.xxx:50001 failed
on local exception: java.io.EOFException]
	 at
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:179)
	 at org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
	 at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
	 at org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
	 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:290)
	 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
	 at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
	 at
com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.j\
ava:371)
	 at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
	 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt\
erChain.java:235)
	 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.\
java:206)
	 at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2\
33)
	 at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1\
91)
	 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
	 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	 at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109\
)
	 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
	 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
	 at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Pr\
otocol.java:588)
	 at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
	 at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.oozie.service.AuthorizationException: E0902: Exception
occured: [java.io.IOException: Call to
namenode.chi.bluekai.com/69.170.130.176:50001 failed on local exception:
java.io.EOFException]
	 at
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:318)
	 at
org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.\
java:171)
	 ... 21 more
Caused by: org.apache.oozie.service.HadoopAccessorException: E0902: Exception
occured: [java.io.IOException: Call to
namenode.chi.bluekai.com/69.170.130.176:50001 failed on local exception:
java.io.EOFException]
	 at
org.apache.oozie.service.KerberosHadoopAccessorService.createFileSystem(Kerberos\
HadoopAccessorService.java:211)
	 at
org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationServi\
ce.java:283)
	 ... 22 more
Caused by: java.io.IOException: Call to
namenode.xxx.xxx.com/xxx.xxx.xxx.xxx:50001 failed on local exception:
java.io.EOFException
	 at org.apache.hadoop.ipc.Client.wrapException(Client.java:1142)
	 at org.apache.hadoop.ipc.Client.call(Client.java:1110)
	 at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:226)
	 at $Proxy22.getProtocolVersion(Unknown Source)
	 at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:398)
	 at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:384)
	 at org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:111)
	 at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:213)
	 at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:180)
	 at
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.ja\
va:89)
	 at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1514)
	 at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:67)
	 at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:1548)
	 at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1530)
	 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:228)
	 at
org.apache.oozie.service.KerberosHadoopAccessorService$3.run(KerberosHadoopAcces\
sorService.java:203)
	 at
org.apache.oozie.service.KerberosHadoopAccessorService$3.run(KerberosHadoopAcces\
sorService.java:194)
	 at java.security.AccessController.doPrivileged(Native Method)
	 at javax.security.auth.Subject.doAs(Subject.java:396)
	 at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1\
127)
	 at
org.apache.oozie.service.KerberosHadoopAccessorService.createFileSystem(Kerberos\
HadoopAccessorService.java:194)
	 ... 23 more
Caused by: java.io.EOFException
	 at java.io.DataInputStream.readInt(DataInputStream.java:375)
	 at org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:815)
	 at org.apache.hadoop.ipc.Client$Connection.run(Client.java:724)

#2037 From: Alejandro Abdelnur <tucu@...>
Date: Thu Aug 25, 2011 5:30 pm
Subject: Re: Re: Oozie error when submitting jobs
tucu0
Send Email Send Email
 
Felix,

It seems your email client has some issues and keeps sending emails to oozie-users@ alias.

You are having issues with CDH setup and it is not appropriate to use the oozie-users@ alias, you should use the cdh-user@... alias.

To help you resolve your mail issue, please resend your email to the cdh-users@... alias and I'll try to help you there.

Thanks for understanding.

Alejandro

On Thu, Aug 25, 2011 at 10:19 AM, Felix <felixgao@...> wrote:
I have added
 <property>
       <name>hadoop.proxyuser.oozie.hosts</name>
        <value>*</value>
    </property>
    <property>
       <name>hadoop.proxyuser.oozie.groups</name>
       <value>*</value>
    </property>

to the core-site.xml on namenode.   After restart namenode,  I still see the following exceptions.

2011-08-25 11:46:09,477  WARN V1JobsServlet:528 - USER[felix] GROUP[users] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[POST http://localhost:11000/oozie/v1/jobs?jobtype=pig] error[E0902], E0902: Exception occured: [java.io.IOException: Call to namenode.xxx.xxx.com/xxx.xxx.xxx.xxx:50001 failed on local exception: java.io.EOFException]
org.apache.oozie.servlet.XServletException: E0902: Exception occured: [java.io.IOException: Call to namenode.xxx.xxx.com/xxx.xxx.xxx.xxx:50001 failed on local exception: java.io.EOFException]
       at org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:179)
       at org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
       at org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:123)
       at com.cloudera.alfredo.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:371)
       at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:128)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
       at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.oozie.service.AuthorizationException: E0902: Exception occured: [java.io.IOException: Call to namenode.chi.bluekai.com/69.170.130.176:50001 failed on local exception: java.io.EOFException]
       at org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:318)
       at org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:171)
       ... 21 more
Caused by: org.apache.oozie.service.HadoopAccessorException: E0902: Exception occured: [java.io.IOException: Call to namenode.chi.bluekai.com/69.170.130.176:50001 failed on local exception: java.io.EOFException]
       at org.apache.oozie.service.KerberosHadoopAccessorService.createFileSystem(KerberosHadoopAccessorService.java:211)
       at org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:283)
       ... 22 more
Caused by: java.io.IOException: Call to namenode.xxx.xxx.com/xxx.xxx.xxx.xxx:50001 failed on local exception: java.io.EOFException
       at org.apache.hadoop.ipc.Client.wrapException(Client.java:1142)
       at org.apache.hadoop.ipc.Client.call(Client.java:1110)
       at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:226)
       at $Proxy22.getProtocolVersion(Unknown Source)
       at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:398)
       at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:384)
       at org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:111)
       at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:213)
       at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:180)
       at org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:89)
       at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1514)
       at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:67)
       at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:1548)
       at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1530)
       at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:228)
       at org.apache.oozie.service.KerberosHadoopAccessorService$3.run(KerberosHadoopAccessorService.java:203)
       at org.apache.oozie.service.KerberosHadoopAccessorService$3.run(KerberosHadoopAccessorService.java:194)
       at java.security.AccessController.doPrivileged(Native Method)
       at javax.security.auth.Subject.doAs(Subject.java:396)
       at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1127)
       at org.apache.oozie.service.KerberosHadoopAccessorService.createFileSystem(KerberosHadoopAccessorService.java:194)
       ... 23 more
Caused by: java.io.EOFException
       at java.io.DataInputStream.readInt(DataInputStream.java:375)
       at org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:815)
       at org.apache.hadoop.ipc.Client$Connection.run(Client.java:724)




------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
   http://groups.yahoo.com/group/Oozie-users/

<*> Your email settings:
   Individual Email | Traditional

<*> To change settings online go to:
   http://groups.yahoo.com/group/Oozie-users/join
   (Yahoo! ID required)

<*> To change settings via email:
   Oozie-users-digest@yahoogroups.com
   Oozie-users-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
   Oozie-users-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
   http://docs.yahoo.com/info/terms/



#2038 From: Mohammad Islam <mislam77@...>
Date: Thu Aug 25, 2011 9:47 pm
Subject: Re: timeout in controls
mislam77@...
Send Email Send Email
 
which version of oozie you are using?


From: vishal.santoshi <vishal.santoshi@...>
To: Oozie-users@yahoogroups.com
Sent: Thursday, August 25, 2011 6:51 AM
Subject: [Oozie-users] timeout in controls

 
According to Coordinator specification timeout's default value is -1

timeout: The maximum time, in minutes, that a materialized action will be waiting for the additional conditions to be satisfied before being discarded. A timeout of 0 indicates that at the time of materialization all the other conditions must be satisfied, else the action will be discarded. A timeout of 0 indicates that if all the input events are not satisfied at the time of action materizlization, the action should timeout immediately. A timeout of -1 indicates no timeout, the materialized action will wait forever for the other conditions to be satisfied. The default value is -1 .

I have a

<controls>
<concurrency>1</concurrency>
<execution>FIFO</execution>
</controls>

And thus would assume no timepout. It has to wait indefinitely for data in 's to appear.

Is there any other reason my job is TIMEDOUT ? Note that it does execute when all data is available.

Regards.




#2039 From: Mohammad Islam <mislam77@...>
Date: Fri Aug 26, 2011 2:34 am
Subject: Moving mailing list to Apache!!
mislam77@...
Send Email Send Email
 
Hi Oozie-user,
Since we are moving to Apache incubator, from now, we will use the Aapche provided user list for communications.

Please subscribe to the user list by sending an email to oozie-user-subscribe@....
If you want to join the dev discussion, send email to oozie-dev-subscribe@....

Then start posting your comments to oozie-user@....

We are going to stop accepting any new user in the current yahoo group from now.
From Sept 2nd, the message posted to the yahoo user group might not get the response that it used to.

We plan to migrate in stages. JIRA is already in Apache. Mailing list is migrating. Code will be in Apache SVN in a week or so. Please keep patient with us during this transition.


Regards,
Mohammad

#2040 From: Alejandro Abdelnur <tucu@...>
Date: Fri Aug 26, 2011 4:01 pm
Subject: PRs 816/817/818
tucu0
Send Email Send Email
 
I've just posted the above PRs (they should be applied in that order),
they fix the postgres config file for testing, set the 2.3.2 release
version in the POMs and set the new devel version 2.3.3-SNAPSHOT.

It would be great if we can push this PRs today, so they are part of
the original Apache import.

Thanks.

Alejandro

#2041 From: "vishal.santoshi" <vishal.santoshi@...>
Date: Fri Aug 26, 2011 5:20 pm
Subject: Re: timeout in controls
vishal.santoshi
Send Email Send Email
 
It seems to be the version. In oozie-2.3.0-cdh3u0 , timeout is not even a valid
schema element.

Any ideas  what the timeout is hardcoded as in oozie-2.3.0-cdh3u0 ?



--- In Oozie-users@yahoogroups.com, Mohammad Islam <mislam77@...> wrote:
>
> which version of oozie you are using?
>
>
>
> ________________________________
> From: vishal.santoshi <vishal.santoshi@...>
> To: Oozie-users@yahoogroups.com
> Sent: Thursday, August 25, 2011 6:51 AM
> Subject: [Oozie-users] timeout in controls
>
>
>  
> According to Coordinator specification timeout's default value is -1
>
> timeout: The maximum time, in minutes, that a materialized action will be
waiting for the additional conditions to be satisfied before being discarded. A
timeout of 0 indicates that at the time of materialization all the other
conditions must be satisfied, else the action will be discarded. A timeout of 0
indicates that if all the input events are not satisfied at the time of action
materizlization, the action should timeout immediately. A timeout of -1
indicates no timeout, the materialized action will wait forever for the other
conditions to be satisfied. The default value is -1 .
>
> I have a
>
> <controls>
> <concurrency>1</concurrency>
> <execution>FIFO</execution>
> </controls>
>
> And thus would assume no timepout. It has to wait indefinitely for data in 's
to appear.
>
> Is there any other reason my job is TIMEDOUT ? Note that it does execute when
all data is available.
>
> Regards.
>

#2042 From: Jeremy Hanna <jeremy.hanna1234@...>
Date: Sun Aug 28, 2011 4:51 am
Subject: Re: status of Apache Incubator?
jeremy_hanna...
Send Email Send Email
 
Cool!  On both counts - a 3.1 release and the move to apache infrastructure. 
Hopefully it will mean greater exposure, adoption, and community involvement.

On Aug 17, 2011, at 3:05 PM, Mohammad Islam wrote:

>
> Hi Alejandro,
> We are working on the last touches of 3.1 release. It should be done in couple
of days.
>
> I will look into those issue after that.
> Btw, we started using Apache JIRA.
>
> Regards,
> Mohammad
>
> From: Alejandro Abdelnur <tucu@...>
> To: oozie-users <Oozie-users@yahoogroups.com>
> Sent: Wednesday, August 17, 2011 12:19 PM
> Subject: [Oozie-users] status of Apache Incubator?
>
>
> What is the status of Oozie incubation?
>
> * When do we switch to Apache Oozie SVN?
> * When do we switch to Apache Oozie email aliases?
> * When do we switch to Apache Oozie JIRA?
> * When do we switch to Apache Oozie Jenkins?
> * How/when are we pushing all GH Issues and Oozie JIRA issues to Apache Oozie
JIRA?
>
> Thanks.
>
> Alejandro
>
>
>
>

#2043 From: Yu Li <carp84@...>
Date: Sun Aug 28, 2011 5:53 pm
Subject: Oozie 2.3.1 Defects on integration with Pig 0.8.1? Three unit test cases failed with Pig 0.8.1 jar files
carp841009
Send Email Send Email
 
Hi all,

Recently I've run unit test on Oozie 2.3.1 with pig-0.8.1.jar, but find the following 3 test cases failed, in all 3 rounds:

testMain(org.apache.oozie.action.hadoop.TestPigMain)
testPig(org.apache.oozie.action.hadoop.TestPigActionExecutor)
testUdfPig(org.apache.oozie.action.hadoop.TestPigActionExecutor)

And looking into the test log, we could find following message:

1) For org.apache.oozie.action.hadoop.TestPigMain, it complains we need the hadoop conf file even in MiniCluster:
==========================================================
11/08/28 08:12:08 INFO pig.Main: Logging error messages to: /home/biadmin/oozie_bluewash/oozie-2.3.1_try_patch_2/core/pig-1314544328128.log
11/08/28 08:12:08 ERROR pig.Main: ERROR 4010: Cannot find hadoop configurations in classpath (neither hadoop-site.xml nor core-site.xml was found in the classpath).If you plan to use local mode, please put -x local option in command line
11/08/28 08:12:08 ERROR pig.Main: org.apache.pig.backend.executionengine.ExecException: ERROR 4010: Cannot find hadoop configurations in classpath (neither hadoop-site.xml nor core-site.xml was found in the classpath).If you plan to use local mode, please put -x local option in command line
        at org.apache.pig.backend.hadoop.executionengine.HExecutionEngine.init(HExecutionEngine.java:169)
        at org.apache.pig.backend.hadoop.executionengine.HExecutionEngine.init(HExecutionEngine.java:134)
==========================================================

2) For testPig and testUdfPig in org.apache.oozie.action.hadoop.TestPigActionExecutor, we could see the following error:
==========================================================
07:49:24,129  INFO DataNode:1004 - PacketResponder 1 for block blk_-6676559698603358313_1044 terminating
07:49:24,129  INFO StateChange:3036 - BLOCK* NameSystem.addStoredBlock: blockMap updated: 127.0.0.1:56044 is added to blk_-6676559698603358313_1044 size 5318
07:49:24,130  INFO StateChange:1400 - DIR* NameSystem.completeFile: file /user/test/oozie-biad/0000000-110828074852223-oozie-biad-W/pig-action--pig/output/_logs/history/localhost_1314542851259_job_20110828074731244_0003_test_oozie%3Alauncher%3AT%3Dpig%3AW%3Dnull%3AA%3Dpig-action%3AID%3D000000 is closed by DFSClient_1779619820
07:49:26,610 ERROR JobEndNotifier:68 - Notification failure [URL: http://localhost:8080/oozie/v0/callback?id=0000000-110828074852223-oozie-biad-W@pig-action&status=SUCCEEDED& remaining retries: 1 interval: 30000]
java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:363)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:225)
==========================================================

The JDK I used is SUN jdk1.6_21, and I only replace the pig jar from 0.7.0 to 0.8.1 in maven repository, leaving all other jars unchanged.

Anybody has met with such failures before? Are these failures defects? Since pig 0.8.1 is commonly used, I think Oozie should be fine to work with it, so please let me know if you have any comments/suggestions. Thanks in advance.

--
Best Regards,
Li Yu


#2044 From: Alejandro Abdelnur <tucu@...>
Date: Sun Aug 28, 2011 11:50 pm
Subject: Re: Oozie 2.3.1 Defects on integration with Pig 0.8.1? Three unit test cases failed with Pig 0.8.1 jar files
tucu0
Send Email Send Email
 
Yu Li,

That has been fixed in GH-483

Oozie 3.0.x and coming Oozie 2.3.2 have this fix.

Thxs.

Alejandro

On Sun, Aug 28, 2011 at 10:53 AM, Yu Li <carp84@...> wrote:


Hi all,

Recently I've run unit test on Oozie 2.3.1 with pig-0.8.1.jar, but find the following 3 test cases failed, in all 3 rounds:

testMain(org.apache.oozie.action.hadoop.TestPigMain)
testPig(org.apache.oozie.action.hadoop.TestPigActionExecutor)
testUdfPig(org.apache.oozie.action.hadoop.TestPigActionExecutor)

And looking into the test log, we could find following message:

1) For org.apache.oozie.action.hadoop.TestPigMain, it complains we need the hadoop conf file even in MiniCluster:
==========================================================
11/08/28 08:12:08 INFO pig.Main: Logging error messages to: /home/biadmin/oozie_bluewash/oozie-2.3.1_try_patch_2/core/pig-1314544328128.log
11/08/28 08:12:08 ERROR pig.Main: ERROR 4010: Cannot find hadoop configurations in classpath (neither hadoop-site.xml nor core-site.xml was found in the classpath).If you plan to use local mode, please put -x local option in command line
11/08/28 08:12:08 ERROR pig.Main: org.apache.pig.backend.executionengine.ExecException: ERROR 4010: Cannot find hadoop configurations in classpath (neither hadoop-site.xml nor core-site.xml was found in the classpath).If you plan to use local mode, please put -x local option in command line
        at org.apache.pig.backend.hadoop.executionengine.HExecutionEngine.init(HExecutionEngine.java:169)
        at org.apache.pig.backend.hadoop.executionengine.HExecutionEngine.init(HExecutionEngine.java:134)
==========================================================

2) For testPig and testUdfPig in org.apache.oozie.action.hadoop.TestPigActionExecutor, we could see the following error:
==========================================================
07:49:24,129  INFO DataNode:1004 - PacketResponder 1 for block blk_-6676559698603358313_1044 terminating
07:49:24,129  INFO StateChange:3036 - BLOCK* NameSystem.addStoredBlock: blockMap updated: 127.0.0.1:56044 is added to blk_-6676559698603358313_1044 size 5318
07:49:24,130  INFO StateChange:1400 - DIR* NameSystem.completeFile: file /user/test/oozie-biad/0000000-110828074852223-oozie-biad-W/pig-action--pig/output/_logs/history/localhost_1314542851259_job_20110828074731244_0003_test_oozie%3Alauncher%3AT%3Dpig%3AW%3Dnull%3AA%3Dpig-action%3AID%3D000000 is closed by DFSClient_1779619820
07:49:26,610 ERROR JobEndNotifier:68 - Notification failure [URL: http://localhost:8080/oozie/v0/callback?id=0000000-110828074852223-oozie-biad-W@pig-action&status=SUCCEEDED& remaining retries: 1 interval: 30000]
java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:363)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:225)
==========================================================

The JDK I used is SUN jdk1.6_21, and I only replace the pig jar from 0.7.0 to 0.8.1 in maven repository, leaving all other jars unchanged.

Anybody has met with such failures before? Are these failures defects? Since pig 0.8.1 is commonly used, I think Oozie should be fine to work with it, so please let me know if you have any comments/suggestions. Thanks in advance.

--
Best Regards,
Li Yu





#2045 From: Alejandro Abdelnur <tucu@...>
Date: Mon Aug 29, 2011 5:11 pm
Subject: PR 818
tucu0
Send Email Send Email
 

Would be possible to integrate PR 818 in branch 2.3 today?
With this we'd be doing the last 2.3.x release before moving to Apache.

Thxs.

Alejandro

#2046 From: Mohammad Islam <mislam77@...>
Date: Mon Aug 29, 2011 8:13 pm
Subject: Re: PR 818
mislam77@...
Send Email Send Email
 
Done.


From: Alejandro Abdelnur <tucu@...>
To: oozie-users <Oozie-users@yahoogroups.com>
Sent: Monday, August 29, 2011 10:11 AM
Subject: [Oozie-users] PR 818

 

Would be possible to integrate PR 818 in branch 2.3 today?
With this we'd be doing the last 2.3.x release before moving to Apache.

Thxs.

Alejandro



#2047 From: Alejandro Abdelnur <tucu@...>
Date: Mon Aug 29, 2011 8:19 pm
Subject: Re: PR 818
tucu0
Send Email Send Email
 
Thanks Mohammad.

Alejandro

On Mon, Aug 29, 2011 at 1:13 PM, Mohammad Islam <mislam77@...> wrote:


Done.


From: Alejandro Abdelnur <tucu@...>
To: oozie-users <Oozie-users@yahoogroups.com>
Sent: Monday, August 29, 2011 10:11 AM
Subject: [Oozie-users] PR 818

 

Would be possible to integrate PR 818 in branch 2.3 today?
With this we'd be doing the last 2.3.x release before moving to Apache.

Thxs.

Alejandro






#2048 From: Yu Li <carp84@...>
Date: Tue Aug 30, 2011 2:34 am
Subject: Re: Oozie 2.3.1 Defects on integration with Pig 0.8.1? Three unit test cases failed with Pig 0.8.1 jar files
carp841009
Send Email Send Email
 
Thanks, Alejandro, for the quick response!

-- 
Best Regards,
Li Yu

On 29 August 2011 07:50, Alejandro Abdelnur <tucu@...> wrote:
 

Yu Li,


That has been fixed in GH-483

Oozie 3.0.x and coming Oozie 2.3.2 have this fix.

Thxs.

Alejandro

On Sun, Aug 28, 2011 at 10:53 AM, Yu Li <carp84@...> wrote:


Hi all,

Recently I've run unit test on Oozie 2.3.1 with pig-0.8.1.jar, but find the following 3 test cases failed, in all 3 rounds:

testMain(org.apache.oozie.action.hadoop.TestPigMain)
testPig(org.apache.oozie.action.hadoop.TestPigActionExecutor)
testUdfPig(org.apache.oozie.action.hadoop.TestPigActionExecutor)

And looking into the test log, we could find following message:

1) For org.apache.oozie.action.hadoop.TestPigMain, it complains we need the hadoop conf file even in MiniCluster:
==========================================================
11/08/28 08:12:08 INFO pig.Main: Logging error messages to: /home/biadmin/oozie_bluewash/oozie-2.3.1_try_patch_2/core/pig-1314544328128.log
11/08/28 08:12:08 ERROR pig.Main: ERROR 4010: Cannot find hadoop configurations in classpath (neither hadoop-site.xml nor core-site.xml was found in the classpath).If you plan to use local mode, please put -x local option in command line
11/08/28 08:12:08 ERROR pig.Main: org.apache.pig.backend.executionengine.ExecException: ERROR 4010: Cannot find hadoop configurations in classpath (neither hadoop-site.xml nor core-site.xml was found in the classpath).If you plan to use local mode, please put -x local option in command line
        at org.apache.pig.backend.hadoop.executionengine.HExecutionEngine.init(HExecutionEngine.java:169)
        at org.apache.pig.backend.hadoop.executionengine.HExecutionEngine.init(HExecutionEngine.java:134)
==========================================================

2) For testPig and testUdfPig in org.apache.oozie.action.hadoop.TestPigActionExecutor, we could see the following error:
==========================================================
07:49:24,129  INFO DataNode:1004 - PacketResponder 1 for block blk_-6676559698603358313_1044 terminating
07:49:24,129  INFO StateChange:3036 - BLOCK* NameSystem.addStoredBlock: blockMap updated: 127.0.0.1:56044 is added to blk_-6676559698603358313_1044 size 5318
07:49:24,130  INFO StateChange:1400 - DIR* NameSystem.completeFile: file /user/test/oozie-biad/0000000-110828074852223-oozie-biad-W/pig-action--pig/output/_logs/history/localhost_1314542851259_job_20110828074731244_0003_test_oozie%3Alauncher%3AT%3Dpig%3AW%3Dnull%3AA%3Dpig-action%3AID%3D000000 is closed by DFSClient_1779619820
07:49:26,610 ERROR JobEndNotifier:68 - Notification failure [URL: http://localhost:8080/oozie/v0/callback?id=0000000-110828074852223-oozie-biad-W@pig-action&status=SUCCEEDED& remaining retries: 1 interval: 30000]
java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:363)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:225)
==========================================================

The JDK I used is SUN jdk1.6_21, and I only replace the pig jar from 0.7.0 to 0.8.1 in maven repository, leaving all other jars unchanged.

Anybody has met with such failures before? Are these failures defects? Since pig 0.8.1 is commonly used, I think Oozie should be fine to work with it, so please let me know if you have any comments/suggestions. Thanks in advance.

--
Best Regards,
Li Yu









#2049 From: Alejandro Abdelnur <tucu@...>
Date: Tue Aug 30, 2011 1:42 pm
Subject: Moving to new alias, oozie-dev@...
tucu0
Send Email Send Email
 
Dear Oozie users and developers,

As part of the Oozie move to the Apache Incubator we are getting a new email alias.

The new email alias is oozie-dev@...

To subscribe to the new email alias send an email to oozie-dev-subscribe@... and reply to the confirmation email.

To avoid confusion and/or stale messages, the oozie-users@yahoogroups.com alias has been disabled.

Looking forward to see you all in the new alias.

Thanks and best regards.

Alejandro (on behalf of the Oozie developers)


#2050 From: Alejandro Abdelnur <tucu@...>
Date: Thu Sep 1, 2011 4:33 pm
Subject: REMINDER - Moving to new alias, oozie-dev@...
tucu0
Send Email Send Email
 
As part of the Oozie move to the Apache Incubator we are getting a new email alias.

The new email alias is oozie-dev@...

To subscribe to the new email alias send an email to oozie-dev-subscribe@... and reply to the confirmation email.

To avoid confusion and/or stale messages, the oozie-users@yahoogroups.com alias has been disabled.

Looking forward to see you all in the new alias.

Thanks and best regards.

Alejandro (on behalf of the Oozie developers)




#2051 From: Alejandro Abdelnur <tucu@...>
Date: Thu Sep 1, 2011 6:35 pm
Subject: REMINDER & CORRECTION - Moving to new aliases, oozie-dev@... and oozie-users@...
tucu0
Send Email Send Email
 

Correction, we have 2 different aliases in Apache Incubator.

  Oozie Developers: oozie-dev@...

  Oozie Users: oozie-users@...

To subscribe send an email to the following email addresses:

  Oozie Developers: oozie-dev-subscribe@...


Apologies for the confusion.

Thanks.

Alejandro

---------- Forwarded message ----------
From: Alejandro Abdelnur <tucu@...>
Date: Thu, Sep 1, 2011 at 9:33 AM
Subject: REMINDER - Moving to new alias, oozie-dev@...
To: oozie-users <Oozie-users@yahoogroups.com>


As part of the Oozie move to the Apache Incubator we are getting a new email alias.

The new email alias is oozie-dev@...

To subscribe to the new email alias send an email to oozie-dev-subscribe@... and reply to the confirmation email.

To avoid confusion and/or stale messages, the oozie-users@yahoogroups.com alias has been disabled.

Looking forward to see you all in the new alias.

Thanks and best regards.

Alejandro (on behalf of the Oozie developers)





Messages 2022 - 2051 of 2051   Oldest  |  < Older  |  Newer >  |  Newest
Add to My Yahoo!      XML What's This?

Copyright © 2010 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines NEW - Help