In the log I see 2014-10-06 11:13:59,822 ERROR [phoenix-2-thread-0] org.apache.phoenix.mapreduce.CsvBulkLoadTool: Import job on table=CDRINFO failed due to 2014-10-06 11:13:59,822 WARN [phoenix-2-thread-0] org.apache.hadoop.security.UserGroupInformation: PriviledgedActionException as:nobody (auth:SIMPLE) cause:java.io.FileNotFoundException: File does not exist: hdfs://dc50-dev-bd01:8020/opt/cloudera/parcels/CDH-5.1.0-1.cdh5.1.0.p0.53/lib/hbase/lib/hbase-server-0.98.1-cdh5.1.0.jar
2014-10-06 11:13:59,822 ERROR [phoenix-2-thread-0] org.apache.phoenix.mapreduce.CsvBulkLoadTool: Import job on table=CDRINFO failed due to exception:java.io.FileNotFoundException: File does not exist: hdfs://dc50-dev-bd01:8020/opt/cloudera/parcels/CDH-5.1.0-1.cdh5.1.0.p0.53/lib/hbase/lib/hbase-server-0.98.1-cdh5.1.0.jar -----Original Message----- From: Gabriel Reid [mailto:[email protected]] Sent: Monday, October 6, 2014 9:39 AM To: [email protected] Cc: Bulvik, Noam Subject: Re: bulk loading using OOZIE Hi Noam, Could you post the error message and/or stack trace you're getting when Oozie says that a jar is missing or you don't have permission to read it? - Gabriel On Sun, Oct 5, 2014 at 8:40 AM, Bulvik, Noam <[email protected]> wrote: > Hi, > > > > We are trying to do periodic bulk loading using OOZIE as scheduler. > We impalement script task that should call the bulk loading command > line with all needed parameter. When we run the script directly from > Linux console it works fine but when we run the OOZIE task it fail > saying that jar is missing or we do not have permission to read it. We > are using CDH5.1 and the jar it companies about is one of the CDh jars > that we checked and it is exists on all machines of the cluster > > > > Any idea ? > > > > Regards, > > Noam > > Information in this e-mail and its attachments is confidential and > privileged under the TEOCO confidentiality terms that can be reviewed here. Information in this e-mail and its attachments is confidential and privileged under the TEOCO confidentiality terms that can be reviewed here<http://www.teoco.com/email-disclaimer>.
