[
https://issues.apache.org/jira/browse/HBASE-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419271#comment-13419271
]
Andrew Purtell edited comment on HBASE-6432 at 7/20/12 3:44 PM:
----------------------------------------------------------------
However, the master is responsible for publishing the cluster ID to ZooKeeper.
If on a fresh install the regionservers are started first, then they won't find
the ID up in ZK until the master comes up. I think this should be a Chore that
retries until the ID is found then exits.
was (Author: apurtell):
However, the master is responsible for publishing the cluster ID to
ZooKeeper. If on a fresh install the regionservers are started first, then they
won't find the ID up in ZK. I think this should be a Chore that retries until
the ID is found then exits.
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
