This sounds like a bug in the implementation of reconfigEnabled. Could you please open a JIRA with the description you provided ?
Out of curiosity, why do you disable reconfig ? It is intended exactly to perform the changes you're trying to make, in a simple and correct way. Thanks, Alex On Thu, Jun 22, 2017 at 3:17 PM, Guillermo Vega-Toro <[email protected]> wrote: > I'm still unable to make configuration changes when reconfigEnabled=false > by updating zoo.cfg and restarting the servers. > > For example, I want to change the weight of one of my servers. I edit > zoo.cfg on the server I want to change, and specify the group, server.x, > and weight.x properties for all servers. I also remove the > dynamicConfigFile property and delete the dynamic config file. I then > restart the server. As soon as the server starts, the dynamic config file > re-appears, and it has the last configuration, as if the changes I made in > zoo.cfg were ignored. The dynamic configuration file on the other servers > also stays the same. > > What would be the correct way to achieve this (change a server's weight, > or role) when reconfigEnabled=false and the CLI reconfig command cannot be > used? > > Thanks > >
