[ 
https://issues.apache.org/jira/browse/HBASE-10282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chendihao updated HBASE-10282:
------------------------------

    Description: 
Thanks to HBASE-10274, we're able to run multiple zk servers in minicluster. 
However, It's confusing to keep the variable activeZKServerIndex as zero and 
assure the first zk server is always the active one. I think returning the 
first sever's client port is for testing and it seems that we can directly 
return the first item of the list. Anyway, the concept of "active" here is not 
the same as zk's. 

It's confusing when I read the code so I think we should fix it.

  was:
Thanks to https://issues.apache.org/jira/browse/HBASE-10274, we're able to run 
multiple zk servers in minicluster. However, It's confusing to keep the 
variable activeZKServerIndex as zero and assure the first zk server is always 
the active one. I think returning the first sever's client port is for testing 
and it seems that we can directly return the first item of the list. Anyway, 
the concept of "active" here is not the same as zk's. 

It's confusing when I read the code so I think we should fix it.


> We can't assure that the first ZK server is active server in 
> MiniZooKeeperCluster
> ---------------------------------------------------------------------------------
>
>                 Key: HBASE-10282
>                 URL: https://issues.apache.org/jira/browse/HBASE-10282
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.3
>            Reporter: chendihao
>            Priority: Minor
>
> Thanks to HBASE-10274, we're able to run multiple zk servers in minicluster. 
> However, It's confusing to keep the variable activeZKServerIndex as zero and 
> assure the first zk server is always the active one. I think returning the 
> first sever's client port is for testing and it seems that we can directly 
> return the first item of the list. Anyway, the concept of "active" here is 
> not the same as zk's. 
> It's confusing when I read the code so I think we should fix it.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to