Error when grant user permissions in HBase: HTTP 403 Error: Grantee user txw387 doesn't exist

[#1]

I want to grant user 'txw387' RWC permissions. There is a hadoop folder 'txw387' under /user.

However, this error occurs: 

ERROR: org.apache.hadoop.hbase.coprocessor.CoprocessorException: HTTP 403 Error: Grantee user txw387 doesn't exist
at org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.preGrant(RangerAuthorizationCoprocessor.java:1277)
at org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.preGrant(RangerAuthorizationCoprocessor.java:1110)
at org.apache.hadoop.hbase.master.MasterCoprocessorHost$164.call(MasterCoprocessorHost.java:1892)
at org.apache.hadoop.hbase.master.MasterCoprocessorHost$164.call(MasterCoprocessorHost.java:1889)
at org.apache.hadoop.hbase.coprocessor.CoprocessorHost$ObserverOperationWithoutResult.callObserver(CoprocessorHost.java:558)
at org.apache.hadoop.hbase.coprocessor.CoprocessorHost.execOperation(CoprocessorHost.java:631)
at org.apache.hadoop.hbase.master.MasterCoprocessorHost.preGrant(MasterCoprocessorHost.java:1889)
at org.apache.hadoop.hbase.master.MasterRpcServices.grant(MasterRpcServices.java:2721)
at org.apache.hadoop.hbase.shaded.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)
at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)

For usage try 'help "grant"'

How to solve this problem?

[#2]

@shubham_sharma @pajoshi @smdas Hi! Do you have any insights here? Thanks!

[#3 · Accepted solution]

Hi @MaraWang 

The error indicates you are using ranger to manage the permissions on hbase. Try to open the ranger WebUi and add the permissions for user under hbase policy.

Also, verify if the user 'txw387' exists in your cluster

Ref-

https://docs.cloudera.com/runtime/7.2.18/security-ranger-authorization/topics/security-ranger-resour...

[#4]

Hi @MaraWang it seems like the user itself is not present in ranger, you need to sync the user from your sync source for ranger, and after that, you need to prove RWX access on hdfs path "/user" under ranger -> cm_hdfs repo, either create a new policy for this or add into an existing one.

[#5]

@MaraWang 

Have you been able to resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. 

mark as solution button