hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6432) HRegionServer doesn't properly set clusterId in conf
Date Fri, 20 Jul 2012 15:37:36 GMT

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

Andrew Purtell commented on HBASE-6432:

Seems reasonable and low risk to pull the ID from ZooKeeper.
> HRegionServer doesn't properly set clusterId in conf
> ----------------------------------------------------
>                 Key: HBASE-6432
>                 URL: https://issues.apache.org/jira/browse/HBASE-6432
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.0
>            Reporter: Francis Liu
>            Assignee: Francis Liu
>             Fix For: 0.96.0
>         Attachments: HBASE-6432_94.patch
> ClusterId is normally set into the passed conf during instantiation of an HTable class.
In the case of a HRegionServer this is bypassed and set to "default" since getMaster() since
it uses HBaseRPC to create the proxy directly and bypasses the class which retrieves and sets
the correct clusterId. 
> This becomes a problem with clients (ie within a coprocessor) using delegation tokens
for authentication. Since the token's service will be the correct clusterId and while the
TokenSelector is looking for one with service "default".

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


View raw message