[ https://issues.apache.org/jira/browse/HBASE-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450539#comment-13450539 ]
Hudson commented on HBASE-6432: ------------------------------- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #164 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/164/]) HBASE-6432 HRegionServer doesn't properly set clusterId in conf (Revision 1381905) Result = FAILURE stack : Files : * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestClusterId.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