hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rakesh Radhakrishnan <rake...@apache.org>
Subject Re: Error in Hbase backup from secure to normal cluster.
Date Mon, 11 Jul 2016 12:43:44 GMT

Hope you are executing 'distcp' command from the secured cluster. Are you
executing the command from a non-super user? Please explain me the
command/way you are executing to understand, how you are entering "entered
super user credentials" and -D command line args.

Also, please share your hdfs-site.xml, core-site.xml configurations.

Have you modified any of these configurations or passed as -D command line

In core-site.xml on the secure cluster side:

In hdfs-site.xml on the secure cluster side:
  <description>This is by default set to an arbitrary string "superuser",
which is
    mostly a non existing group on most (all?) environments. Changing this
    and/or creating such a group name on the NN machine will let you
    permit more users to act as superusers, if needed.

Again, I'd suggest you to post this problem to the hbase user mailing list
to know any specific configurations from HBase side.


On Mon, Jul 11, 2016 at 3:45 PM, mathes waran <matheskrishna@gmail.com>

> Hi,
> I tried distcp method in hbase backup from secure to normal cluster,In my
> backup job the data is transferred successfully from secure to normal
> cluster,but in resource manager job id is shown as failed due to error of
> Non super user cannot change owner.
> However, table and snapshot is created successfully and restoring table
> from normal to secure is executed successfully.
> But in HBase backup due to this error ,application Id is shown as failed.
> Please find the error details as below:
> *Caused by:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
> Non-super user cannot change owner*
> Even I entered super user credentials while executing distcp job from
> secure to normal cluster,this exception is occurred.
> please note that,this error is occurred only on backup from secure to
> normal,and its not occur on restoring table.
> Can u pls tell me is there any changes in configuration file or how could
> i solve this..?
> Looking back.!
> Thanks,
> Matheskrishna

View raw message