You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Andrew Ferguson (JIRA)" <ji...@apache.org> on 2012/08/23 19:59:42 UTC

[jira] [Updated] (ZOOKEEPER-1540) ZOOKEEPER-1411 breaks backwards compatibility

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Ferguson updated ZOOKEEPER-1540:
---------------------------------------

    Attachment: ZOOKEEPER-1540.patch

this bug occurs if you have a separate configuration file for each ZooKeeper server (as in previous releases) and have clientPort specified as part of the file, rather than as part of the "server.N=host:port:port:type;host:port" format introduced by ZOOKEEPER-1411 (I hope I'm reading that patch correctly).

not sure how to write a test case for this -- if one's needed, perhaps someone can suggest how? thank you.
                
> ZOOKEEPER-1411 breaks backwards compatibility
> ---------------------------------------------
>
>                 Key: ZOOKEEPER-1540
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1540
>             Project: ZooKeeper
>          Issue Type: Bug
>            Reporter: Andrew Ferguson
>         Attachments: ZOOKEEPER-1540.patch
>
>
> There is a one-line bug in ZOOKEEPER-1411 which breaks backwards compatibility for sites which are using separate configuration files for each server. The bug is with the handling of the clientPort option.
> One line fix to follow shortly.
> thanks!
> Andrew

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira