Gary and Andrew,
Many thanks for your help. Now we can move a step forward. :-)
Demai
On Fri, Jun 20, 2014 at 10:26 AM, Gary Helmling wrote:
> Hi Demai,
>
> Yes, even when using hbase.security.authentication=simple in 0.94, you need
> to use SecureRpcEngine. The default WritableRpcEngine doe
Hi Demai,
Yes, even when using hbase.security.authentication=simple in 0.94, you need
to use SecureRpcEngine. The default WritableRpcEngine does not pass the
username to the server at all, which can obviously cause problems for
authorization.
--gh
On Fri, Jun 20, 2014 at 10:21 AM, Demai Ni wr
hi, Andrew,
I didn't setup the keytabs as the current setup is using a firewall instead
of kerberos. so only use the authorization feature of hbase, and not
authentication at this moment. A long story about why. :-(
Anyway, I got a tip here
http://www.cloudera.com/content/cloudera-content/clouder
Have you set up keytabs for the server processes?
On Thu, Jun 19, 2014 at 9:40 PM, Demai Ni wrote:
> hi, folks,
>
> I am able to recreate the same error on another single node cluster.
>
> RS log pasted here: http://pastebin.com/iP9Mrz2T
> and
> hbase-site.xml is here: http://pastebin.com/ppnqf
hi, folks,
I am able to recreate the same error on another single node cluster.
RS log pasted here: http://pastebin.com/iP9Mrz2T
and
hbase-site.xml is here: http://pastebin.com/ppnqfwGR
the only thing changes is by adding the following property per
http://hbase.apache.org/book/hbase.accesscontro
Hi All,
I am running HBase 0.94.3 and trying to get ACL working on a single node
cluster. I followed the steps in
http://hbase.apache.org/book/hbase.accesscontrol.configuration.html step
8.4.3 and added those 2 properties to my hbase-site.xml
After stopping and starting hbase, my regionserver is
