[
https://issues.apache.org/jira/browse/ZOOKEEPER-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789852#comment-13789852
]
Alexander Shraer commented on ZOOKEEPER-1499:
---------------------------------------------
I tried this: clientPort is being read, but if you specified both clientPort
and the port in the new format (after ;) they must be the same.
Same for clientPortAddress.
But seems like Camille is right in her comment that if you specified the
clientPort with the new format you won't be able to connect to it using
localhost. I'm not sure if this is a problem but I'm guessing that it may be
because previously if you just specified clientPort, the IP was taken as
localhost implicitly. Whereas now if you say "a:b:c;d", a is taken as the ip
for d. To achieve the same as before you can write "a:b:c;localhost:d".
While trying this I found a corner case missing in zkServer.sh -- if the
specification uses the new format but still appears in the static configuration
file (backward compatibility), zkServer.sh won't find the port (for example if
you say ./bin/zkServer.sh status it will complain). Attached is a small patch
for this.
> clientPort config changes not backwards-compatible
> --------------------------------------------------
>
> Key: ZOOKEEPER-1499
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1499
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.5.0
> Reporter: Camille Fournier
> Assignee: Benjamin Reed
> Priority: Blocker
>
> With the new reconfig logic, clientPort=2181 in the zoo.cfg file no longer
> gets read, and clients can't connect without adding ;2181 to the end of their
> server lines.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
