[
https://issues.apache.org/jira/browse/ZOOKEEPER-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235461#comment-13235461
]
Flavio Junqueira commented on ZOOKEEPER-1411:
---------------------------------------------
@Alex You're right, I hadn't looked into setType.
@Rakesh If you check the first comment of this jira, in the sample config, it
sounds like Alex is proposing this new pattern: hostname:port:port:type. We
currently don't use such a pattern host:port:type, at least according to the
documentation and to my knowledge. I'm also not sure I understand the comment
about the NFE propagating back in the call chain. Why is that an issue exactly?
> 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
