zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shraer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2445) Add a new node to cluster, error config file but sucessed
Date Wed, 08 Jun 2016 14:34:21 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320645#comment-15320645

Alexander Shraer commented on ZOOKEEPER-2445:

First if you're interested in adding/removing nodes, consider using 3.5 release and the reconfiguration
API. https://zookeeper.apache.org/doc/trunk/zookeeperReconfig.html

>  the server does not match with the serverid

which server ? the new one ? I don't really understand what you mean here. Could you paste
here the configuration file of the new server, and its myid. But essentially, the server is
only supposed to make sure that myid appears in the configuration file (when booting), not
much more than that. What check would you expect ?

> Add a new node to cluster, error config file but sucessed
> ---------------------------------------------------------
>                 Key: ZOOKEEPER-2445
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2445
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.4.6
>         Environment: Centos 6.5 JDK7
>            Reporter: Ahaha
>            Priority: Critical
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> I want to add a new node to a test cluster with three node. So I tried with the folling
steps: 1. I copied one foller zookeeper directory, and edit clientPort, dataDir , logDir,
myid file, and then add a new record server.newId=hostname:newPort:newEPort into zoo.cfg,
for test I keep the leader configuration there and remove the other two configuration, I tested
,this failed. So I open the zoo.cfg , copied the lead configuration line just edit the serverId,
and this should be a wrong configuration file as the server does not match with the serverid.
But strangely , it successed. 

This message was sent by Atlassian JIRA

View raw message