You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Francis Liu (JIRA)" <ji...@apache.org> on 2012/08/31 19:27:08 UTC

[jira] [Updated] (HBASE-6432) HRegionServer doesn't properly set clusterId in conf

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

Francis Liu updated HBASE-6432:
-------------------------------

    Attachment: HBASE-6432.patch

Here's patch of what I described. Let me know if this is ok and I'll come up with an 0.94 patch.
                
> 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, 0.96.0
>            Reporter: Francis Liu
>            Assignee: Francis Liu
>         Attachments: HBASE-6432_94.patch, HBASE-6432.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
For more information on JIRA, see: http://www.atlassian.com/software/jira