[
https://issues.apache.org/jira/browse/HBASE-19793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325289#comment-16325289
]
stack commented on HBASE-19793:
-------------------------------
I made a change in ordering yesterday. ClusterId was set in fs, and on master
becoming active, up in zk... but the clusterid was NOT being set in the process
until after regionserver had checked in with master -- post reportForDuty.
Change made yesterday was that master sets the clusterid into process after
setting into zk. It no longer waits for regionserver#run and reportForDuty.
https://github.com/apache/hbase/commit/4ddfecac563384de6f087fc7fc8bc62c0362877d#diff-910fe86f307ab33e4e946c666e739972R802
Maybe you had something diffferent in mind?
> Move the cluster id initialization to the very beginning
> --------------------------------------------------------
>
> Key: HBASE-19793
> URL: https://issues.apache.org/jira/browse/HBASE-19793
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Fix For: 2.0.0-beta-1
>
>
> Both ZooKeeper and hadoop FileSystem can do fencing, that means, if two
> processes try to create one file, only one of them can succeed. So I think we
> can move the initialization of ClusterId to the very beginning instead of
> only allow active master to do it.
> This may helps us solve the complicated dependency issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
