[
https://issues.apache.org/jira/browse/ZOOKEEPER-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235187#comment-13235187
]
Alexander Shraer commented on ZOOKEEPER-1411:
---------------------------------------------
In the case you describe, when NumberFormatException is thrown, setType is
called, and if the parameter is neither "participant" nor "observer", an
exception is thrown by setType. If its one of these types, then the function
returns and we continue normally knowing that we got host:port:type (which
would be legal for the old LE algorithm)
> Consolidate membership management and add client port information
> -----------------------------------------------------------------
>
> Key: ZOOKEEPER-1411
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1411
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: server
> Reporter: Alexander Shraer
> Assignee: Alexander Shraer
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1411-ver1.patch, ZOOKEEPER-1411-ver2.patch,
> ZOOKEEPER-1411-ver3.patch, ZOOKEEPER-1411-ver4.patch,
> ZOOKEEPER-1411-ver5.patch
>
>
> Currently every server has a different configuration file. With this patch,
> we will have all cluster membership definitions in a single file, and every
> sever can have a copy of this file.
> This also solves ZOOKEEPER-1113
--
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
