Looking at the stack trace, it seems to be oozie issue.

Have you mailed user@oozie ?

Thanks

On Wed, Oct 12, 2016 at 3:32 AM, mathes waran <matheskris...@gmail.com>
wrote:

>  Hi,
>
>
> I have setup the Oozie credentials to connect secure HBase secure cluster
> using Java action,, as per documentation from oozie site,
>
> This steps are followed :
>
> 1.           Set oozie.credentials.credentialclasses property in
> oozie-site.xml
>
> 2.           set credentials property in workflow.xml and set the
> credential name within action tag.
>
> 3.           Copied all jars file from Hbase bin to oozie lib folder and
> also in lib folder from WEBINF in oozie-server.
>
> 4.           Similarly Copied  Hbase-site.xml and paste into same both
> locations and restart it.
>
>
>
> Currently now I facing the issues while job submission:
>
>
> *ErrorCode [JA020], Message [JA020: Could not load credentials of type
> [hbase] with name [Securehbase]]; perhaps it was not defined in
> oozie-site.xml?] *
>
>
>
> WARN ActionStartXCommand:523 - SERVER[Node1] USER[Mathes] GROUP[-] TOKEN[]
> APP[hbaseTable-wf] JOB[0000204-161011213057744-oozie-xxxx-W]
> ACTION[0000204-161011213057744-oozie-xxxx-W@TableBackup] Error starting
> action [TableBackup]. ErrorType [ERROR], ErrorCode [JA020], Message [JA020:
> Could not load credentials of type [hbase] with name [Securehbase]];
> perhaps it was not defined in oozie-site.xml?]
> org.apache.oozie.action.ActionExecutorException: JA020: Could not load
> credentials of type [hbase] with name [Securehbase]]; perhaps it was not
> defined in oozie-site.xml? at
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(
> JavaActionExecutor.java:1211)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(
> JavaActionExecutor.java:1066)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.
> start(JavaActionExecutor.java:1286)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(
> ActionStartXCommand.java:250)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(
> ActionStartXCommand.java:64)
> at org.apache.oozie.command.XCommand.call(XCommand.java:286) at
> org.apache.oozie.command.XCommand.call(XCommand.java:356) at
> org.apache.oozie.command.wf.SignalXCommand.execute(
> SignalXCommand.java:434)
> at
> org.apache.oozie.command.wf.SignalXCommand.execute(SignalXCommand.java:76)
> at org.apache.oozie.command.XCommand.call(XCommand.java:286) at
> org.apache.oozie.command.XCommand.call(XCommand.java:356) at
> org.apache.oozie.command.wf.ActionEndXCommand.execute(
> ActionEndXCommand.java:280)
> at
> org.apache.oozie.command.wf.ActionEndXCommand.execute(
> ActionEndXCommand.java:61)
> at org.apache.oozie.command.XCommand.call(XCommand.java:286) at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(
> CallableQueueService.java:175)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
>
>
>
> Please suggest me if you overcome this.
>
>
>
> Thanks,
>
> Mathes
>

Reply via email to