[
https://issues.apache.org/jira/browse/ZOOKEEPER-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780252#comment-17780252
]
Andor Molnar commented on ZOOKEEPER-4276:
-----------------------------------------
[~abhilash1in]
Looks like you're facing an issue in ZooKeeper which has been present since
ages. I did a quick search in Jira and it was mentioned in 2018 when the
secureClientPort was introduced:
https://issues.apache.org/jira/browse/ZOOKEEPER-2125?focusedCommentId=16638309&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16638309
I don't find an answer for this, so I would say this issue hasn't been
addressed (although it should have been) when the SSL option was implemented.
Would you mind putting together a patch under this Jira?
> Serving only with secureClientPort fails
> ----------------------------------------
>
> Key: ZOOKEEPER-4276
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4276
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.7.0, 3.5.8, 3.6.2, 3.8.0
> Reporter: Kei Kori
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> clientPort in zoo.cfg is forcefully complemented from client address by
> QuorumPeerConfig#setupClientPort even though secureClientPort is set and
> matches with client address' port.
> Because of this behavior, in case rolling update with replacing clientPort to
> secureClientPort in the same port number following [Upgrading existing
> non-TLS cluster with no
> downtime|https://zookeeper.apache.org/doc/r3.7.0/zookeeperAdmin.html#Upgrading+existing+nonTLS+cluster]
> conflicts and gets errors below.
> {code}
> 2021-03-29 23:21:58,638 - INFO [main:NettyServerCnxnFactory@590] - binding
> to port /0.0.0.0:2281
> 2021-03-29 23:21:58,748 - INFO [main:NettyServerCnxnFactory@595] - bound to
> port 2281
> 2021-03-29 23:21:58,749 - INFO [main:NettyServerCnxnFactory@590] - binding
> to port 0.0.0.0/0.0.0.0:2281
> 2021-03-29 23:21:58,753 - ERROR [main:QuorumPeerMain@101] - Unexpected
> exception, exiting abnormally
> java.net.BindException: Address already in use
> {code}
> QuorumPeerConfig#setupClientPort should complement only when both clientPort
> and secureClientPort are empty, and allow serving zookeeper server only with
> secure client port.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
