[
https://issues.apache.org/jira/browse/HBASE-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445091#comment-13445091
]
Francis Liu commented on HBASE-6432:
------------------------------------
[~apurtell] I was working on adding the blocking logic this morning. Looking
at the way the master starts up it looks like it sets the clusterId before
changing cluster status to up. And the HRegionServer already has blocking logic
until clusterStatus is set to up. We can add the retrieval of the clusterId
after this step. Is that a fair assumption to make?
> 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
>
>
> 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
