You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2016/10/21 20:52:58 UTC

[jira] [Commented] (HBASE-16829) DemoClient should detect secure mode

    [ https://issues.apache.org/jira/browse/HBASE-16829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596337#comment-15596337 ] 

Ted Yu commented on HBASE-16829:
--------------------------------

Thanks to Josh who found the case where mismatched user name for hbase.thrift.kerberos.principal led to the mysterious SocketTimeoutException.

> DemoClient should detect secure mode
> ------------------------------------
>
>                 Key: HBASE-16829
>                 URL: https://issues.apache.org/jira/browse/HBASE-16829
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>         Attachments: 16829.v1.txt
>
>
> Sometimes user runs DemoClient against secure cluster using the following command:
> {code}
> java -cp `hbase classpath` org.apache.hadoop.hbase.thrift2.DemoClient host 9090
> {code}
> This wouldn't work.
> DemoClient should detect the presence of secure cluster - e.g. through the following config:
> {code}
>     <property>
>       <name>hbase.thrift.authentication.type</name>
>       <value>kerberos</value>
>     </property>
> {code}
> User can still specify 'false' as the last parameter if the target cluster is insecure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)