Marked the more recent ticket as duplicate.
Thanks Fred.
Andor
> On 2019. Jul 9., at 16:22, Fred Eisele wrote:
>
> There is already an issue .
> https://issues.apache.org/jira/browse/ZOOKEEPER-3166
There is already an issue .
https://issues.apache.org/jira/browse/ZOOKEEPER-3166
https://issues.apache.org/jira/browse/ZOOKEEPER-3458
On Tue, Jul 2, 2019 at 3:43 AM Andor Molnar wrote:
> Got it. Thanks Alex. I’m not familiar with dynamic config unfortunately.
> I agree that we need to open a Jira for it.
>
> Andor
>
>
>
> > On 2019. Jul 2., at 6:55, Alexander Shraer
Got it. Thanks Alex. I’m not familiar with dynamic config unfortunately.
I agree that we need to open a Jira for it.
Andor
> On 2019. Jul 2., at 6:55, Alexander Shraer wrote:
>
> I think that Fred is correct - secureClientPort and secureClientPortAddress
> were not made part of the dynamic
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
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
The server specification is ...
server. = ::[:role];[:]
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?
