zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Nixon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3166) Support changing secure port with reconfig
Date Fri, 12 Oct 2018 19:46:00 GMT

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

Brian Nixon commented on ZOOKEEPER-3166:

It would be cool to see the serialized format of the QuorumVerifier (used for the dynamic
config files and the like) updated to a more extensible form so we can track more topology
and port information through it. A key-value json blob is one such solution.

> Support changing secure port with reconfig
> ------------------------------------------
>                 Key: ZOOKEEPER-3166
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3166
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: quorum
>    Affects Versions: 3.6.0
>            Reporter: Brian Nixon
>            Priority: Minor
> The reconfig operation supports changing the plaintext client port and client address
but, because the secure client port is not encoded in the QuorumVerifier serialization, the
secure client port cannot be changed by similar means. Instead, this information can only
be changed in the static configuration files and only viewed there.
> Flagging as a place where there's not feature parity between secure client ports and
plaintext client ports.

This message was sent by Atlassian JIRA

View raw message