[
https://issues.apache.org/jira/browse/HBASE-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455036#comment-13455036
]
Hudson commented on HBASE-6432:
-------------------------------
Integrated in HBase-0.94-security #52 (See
[https://builds.apache.org/job/HBase-0.94-security/52/])
HBASE-6432 HRegionServer doesn't properly set clusterId in conf (Revision
1381907)
Result = SUCCESS
stack :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
> 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
> Fix For: 0.96.0, 0.94.2
>
> 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
