[
https://issues.apache.org/jira/browse/ZOOKEEPER-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789913#comment-13789913
]
Alexander Shraer commented on ZOOKEEPER-1499:
---------------------------------------------
Hi Camille,
There are two issues pointed out in this JIRA. 1) (in the description)
clientPort no longer gets read and 2) (in your first comment) and a client
can't use localhost:...
I tried but can't reproduce issue 1, seems like clientPort is being read. Thats
why I suggested to close the JIRA.
For issue 2, I think you're right, and I think this follows from how the ip
address is inferred if you don't explicitly specify it.
Previously it was assumed to be 'localhost' whereas now its assumed to be the
ip from the server spec line. I'm not sure if this is a problem.
I moved the patch to zkServer.sh to a separate JIRA - ZOOKEEPER-1785 since it
solves a different problem
> 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: Alexander Shraer
> Priority: Blocker
> Fix For: 3.5.0
>
>
> 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)
