hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19793) Move the cluster id initialization to the very beginning
Date Sun, 14 Jan 2018 12:32:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-19793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325545#comment-16325545
] 

Duo Zhang commented on HBASE-19793:
-----------------------------------

There are bunch of initialization code for a fresh cluster, not only cluster id. So it is
not a good idea to move them into the constructor.

But anyway, let me add some comments and do some refactoring to make the start up code more
readable.

> 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)

Mime
View raw message