[
https://issues.apache.org/jira/browse/ZOOKEEPER-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235626#comment-13235626
]
Flavio Junqueira commented on ZOOKEEPER-1411:
---------------------------------------------
Given that the old LE code is already deprecated (ZOOKEEPER-1153), I would say
that it is fine to not take it into account as Rakesh suggests. I don't feel
too strongly either way. In the case we keep it, it would be a good idea to
create a jira or sub-task for removing it.
I can't find a jira for removing the UDP-based implementations. If there isn't
one, then we need to create one for it too.
> 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
