Rajkiran I am not sure that changing the addresses this way is supported. Apart from that... Maybe you can try to enable reconfig and use it to fix the problem.
Otherwise another way would be to add new nodes with the new addresses and then dismiss the old nodes Enrico Il Sab 2 Mag 2020, 10:42 rajsura <[email protected]> ha scritto: > Latest observation, we noticed that ZooKeeper was complaining about > dynamic.next file, event though we HAVE NOT ENABLED > dynamic-reconfiguration. > > > 2020-05-02 01:43:05,870 [myid:21] - ERROR > [QuorumPeer[myid=21](plain=/0.0.0.0:2181)(secure=disabled):QuorumPeer@1637 > ] > - Error writing next dynamic config file to disk: > > > And zookeeper user did not have perms to that config directory, so we fixed > that restarted zookeeper. And then it dumped below dynamic.next, which > contains the OLD migrated node as a member :O > > > $ sudo cat /opt/zookeeper/conf/zoo.cfg.dynamic.next > server.17=node1.foo.bar.com:2888:3888:participant;0.0.0.0:2181 > server.19=node2.foo.bar.com:2888:3888:participant;0.0.0.0:2181 > server.20=node3.foo.bar.com:2888:3888:participant;0.0.0.0:2181 > server.21=node4.foo.bar.com:2888:3888:participant;0.0.0.0:2181 > server.22=node5.bar.com:2888:3888:participant;0.0.0.0:2181 > > > So, this looks like a bug. And from where is it still fetching this? How do > we fix it. > Any lead/help is very much appreciated. > > FTR: We haven't enabled dynamic reconfig. > > Thanks in advance, > Rajkiran > > > > -- > Sent from: http://zookeeper-user.578899.n2.nabble.com/ >
