- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
user is not allowed to impersonate admin in hbase thrift server
- Labels:
-
Apache HBase
-
Cloudera Hue
-
HDFS
Created on ‎11-29-2016 10:02 AM - edited ‎09-16-2022 03:50 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
i am new in hbase developer, and i have a problem with my hbase.
for the first time, i can use hbase thrift server and can use hbase browser in hue very soft
but when my computer restart, and i start manually again the hbase thrift by command "hbase thrift start" in terminal. it returns "user root/myusername is not allowed to impersonate admin".
i don't know why. i have changed all the configuration.
add "hadoop.proxyuser.hbase.hosts" and "hadoop.proxyuser.hbase.groups" with value "*"
and still don't change the error in the hue web UI.
anybody can help me ?
please i need somebody help, i can't continue my thesis..
thank you very much.
Created ‎11-29-2016 11:57 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
you might try adding the following to core-site.xml seems like the error is talking about the root group.
hadoop.proxyuser.root.groups=* hadoop.proxyuser.root.hosts=*
If you are running cloudera manager, you need to add those in cloudera manager itself, the config is not in the traditional space, but instead in a seperate folder managed by cloudera for each individual service. Confusingly, the config is in the traditional space is for the "gateway".
Created ‎11-29-2016 11:57 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
you might try adding the following to core-site.xml seems like the error is talking about the root group.
hadoop.proxyuser.root.groups=* hadoop.proxyuser.root.hosts=*
If you are running cloudera manager, you need to add those in cloudera manager itself, the config is not in the traditional space, but instead in a seperate folder managed by cloudera for each individual service. Confusingly, the config is in the traditional space is for the "gateway".
