I'm trying to use oozie and copyTable to tranfser Hbase data between two kerborized clusters. My workflow works fine in both directions but only when it is started on source side. What I need is to run the entire workflow on target but launch the copyTable action on souce (remote). When I assign the RM and NN from remote cluster to my copyTable action the workflow starts a launcher job on remote cluster which fails due to invalid deligation token. The log tells me that the launcher job tries to (re)connect to RM on target (where the workflow was started).
Is it possible to run a workflow in that way? What could be reason why it fails?
Meanwhile I found the solution. In addtion to the whitelisting in oozie.service, you have to create hbase credentials for source and target and to assign both to java action. Furthermore you must load hbase-xml from source cluster and configure RMS and JHS. Then it works fine!