You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by mathes waran <ma...@gmail.com> on 2016/10/12 10:32:28 UTC

Support for oozie credentials in Hbase backup

 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

Re: Support for oozie credentials in Hbase backup

Posted by mathes waran <ma...@gmail.com>.
Hi Ted,

Thanks for your response and this problem is resolved due to oozie  error.

I followed by job submission for Oozie  to connect to secure HBase secure
cluster using Java action , as per documentation from oozie site, *initially
the job was submitted without any  issues in cmd prompt but in resource
manager UI ,it’s does not shown anything like accepted or running state.
Job run for long time and it was suspended due to exception in receiving
Hbase credentials org.apache.hadoop.hbase.client.RetriesExhaustedException
and no issues were logged at this time .*

Please find the log after submission of job from console:

2016-10-12 17:12:18,869
INFO ActionStartXCommand:520 - SERVER[NODE1] USER[Matheswaran] GROUP[-]
TOKEN[] APP[hbaseTable-wf] JOB[0000000-161012171001551-oozie-XXXX-W]
ACTION[0000000-161012171001551-oozie-XXXX-W@:start:] Start action
[0000000-161012171001551-oozie-XXXX-W@:start:] with user-retry state :
userRetryCount [0], userRetryMax [0], userRetryInterval [10]

2016-10-12 17:12:18,873
INFO ActionStartXCommand:520 - SERVER[NODE1] USER[Matheswaran] GROUP[-]
TOKEN[] APP[hbaseTable-wf] JOB[0000000-161012171001551-oozie-XXXX-W]
ACTION[0000000-161012171001551-oozie-XXXX-W@:start:]
[***0000000-161012171001551-oozie-XXXX-W@:start:***]Action status=DONE

2016-10-12 17:12:18,873
INFO ActionStartXCommand:520 - SERVER[NODE1] USER[Matheswaran] GROUP[-]
TOKEN[] APP[hbaseTable-wf] JOB[0000000-161012171001551-oozie-XXXX-W]
ACTION[0000000-161012171001551-oozie-XXXX-W@:start:]
[***0000000-161012171001551-oozie-XXXX-W@:start:***]Action updated in DB!

2016-10-12 17:12:19,100
INFO WorkflowNotificationXCommand:520 - SERVER[NODE1] USER[-] GROUP[-]
TOKEN[-] APP[-] JOB[0000000-161012171001551-oozie-XXXX-W]
ACTION[0000000-161012171001551-oozie-XXXX-W@:start:] No Notification URL is
defined. Therefore nothing to notify for job
0000000-161012171001551-oozie-XXXX-W@:start:

2016-10-12 17:12:19,100
INFO WorkflowNotificationXCommand:520 - SERVER[NODE1] USER[-] GROUP[-]
TOKEN[-] APP[-] JOB[0000000-161012171001551-oozie-XXXX-W] ACTION[] No
Notification URL is defined. Therefore nothing to notify for job
0000000-161012171001551-oozie-XXXX-W

2016-10-12 17:12:19,119
INFO ActionStartXCommand:520 - SERVER[NODE1] USER[Matheswaran] GROUP[-]
TOKEN[] APP[hbaseTable-wf] JOB[0000000-161012171001551-oozie-XXXX-W]
ACTION[0000000-161012171001551-oozie-XXXX-W@check-output] Start action
[0000000-161012171001551-oozie-XXXX-W@check-output] with user-retry state :
userRetryCount [0], userRetryMax [0], userRetryInterval [10]

2016-10-12 17:12:19,124
INFO ActionStartXCommand:520 - SERVER[NODE1] USER[Matheswaran] GROUP[-]
TOKEN[] APP[hbaseTable-wf] JOB[0000000-161012171001551-oozie-XXXX-W]
ACTION[0000000-161012171001551-oozie-XXXX-W@check-output]
[***0000000-161012171001551-oozie-XXXX-W@check-output***]Action status=DONE

2016-10-12 17:12:19,124
INFO ActionStartXCommand:520 - SERVER[NODE1] USER[Matheswaran] GROUP[-]
TOKEN[] APP[hbaseTable-wf] JOB[0000000-161012171001551-oozie-XXXX-W]
ACTION[0000000-161012171001551-oozie-XXXX-W@check-output]
[***0000000-161012171001551-oozie-XXXX-W@check-output***]Action updated in
DB!

2016-10-12 17:12:19,249
INFO ActionStartXCommand:520 - SERVER[NODE1] USER[Matheswaran] GROUP[-]
TOKEN[] APP[hbaseTable-wf] JOB[0000000-161012171001551-oozie-XXXX-W]
ACTION[0000000-161012171001551-oozie-XXXX-W@TableBackup] Start action
[0000000-161012171001551-oozie-XXXX-W@TableBackup] with user-retry state :
userRetryCount [0], userRetryMax [0], userRetryInterval [10]

Please suggest how to overcome this,is there need to any set any other
properties apart from documentation.

Thanks,
Mathes.S

On Wed, Oct 12, 2016 at 4:02 PM, mathes waran <ma...@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
>

Re: Support for oozie credentials in Hbase backup

Posted by Ted Yu <yu...@gmail.com>.
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 <ma...@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
>