[ 
https://issues.apache.org/jira/browse/HBASE-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Himanshu Vashishtha updated HBASE-6314:
---------------------------------------

    Description: 
In case of unauthenticated users in secure hbase, hbase shell does a connection 
retry at two levels:
a) HConnection: It retries hbase.client.retries.number times in the getMaster()
b) HBaseAdmin: it again retries hbase.client.retries.number times in its ctr

So, hbase shell retries square number of times of the configured setting. We 
can make it failfast (no retries) in case the user is not authenticated (no 
valid kerberos credentials).

  was:
In case of unauthenticated users in secure hbase, hbase shell does a connection 
retry at two levels:
a) HConnection: It retries hbase.client.retries.number times
b) HTableAdmin: it again retries hbase.client.retries.number times

So, hbase shell retries square number of times of the configured setting. We 
can make it failfast (no retries) in case the user is not authenticated (no 
valid kerberos credentials).

    
> In secure hbase, we should have a fail fast behavoir for unauthenticated user
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-6314
>                 URL: https://issues.apache.org/jira/browse/HBASE-6314
>             Project: HBase
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 0.92.0, 0.94.0
>            Reporter: Himanshu Vashishtha
>            Priority: Minor
>
> In case of unauthenticated users in secure hbase, hbase shell does a 
> connection retry at two levels:
> a) HConnection: It retries hbase.client.retries.number times in the 
> getMaster()
> b) HBaseAdmin: it again retries hbase.client.retries.number times in its ctr
> So, hbase shell retries square number of times of the configured setting. We 
> can make it failfast (no retries) in case the user is not authenticated (no 
> valid kerberos credentials).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to