I think that Fred is correct - secureClientPort and secureClientPortAddress were not made part of the dynamic configuration (yet ?), so unlike other parameters, they are static. Fred, perhaps you could open a Jira to ask for this feature ?
Thanks, Alex On Mon, Jul 1, 2019 at 2:58 PM Andor Molnar <an...@apache.org> wrote: > Hi Fred, > > I don’t think this server spec is accurate. > clientPort and clientPortAddress as well as secureClientPort and > secureClientPortAddress are defined in the main section of config file, not > within Cluster Options: > > > https://zookeeper.apache.org/doc/r3.5.5/zookeeperAdmin.html#sc_configuration > < > https://zookeeper.apache.org/doc/r3.5.5/zookeeperAdmin.html#sc_configuration > > > > e.g. You should have something like: > > clientPort=2181 > clientPortAddress=127.0.0.1 > secureClientPort=1181 > secureClientPortAddress=… > > server.1=… > server.2=… > > In your zoo.cfg config file. > > Regards, > Andor > > > > > On 2019. Jun 19., at 17:28, Fred Eisele <fredrick.eis...@gmail.com> > wrote: > > > > The server specification is ... > > server.<positive id> = <address1>:<port1>:<port2>[:role];[<client port > > address>:]<client port> > > The clientPort and clientPortAddress are accomodated but I do not see a > > provision for secureClientPort. > > I presume this means it is a static parameter as before? > >
