You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Skye Wanderman-Milne (JIRA)" <ji...@apache.org> on 2012/12/04 03:25:58 UTC

[jira] [Updated] (ZOOKEEPER-1346) Handle 4lws and monitoring on separate port

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

Skye Wanderman-Milne updated ZOOKEEPER-1346:
--------------------------------------------

    Attachment: ZOOKEEPER-1346.2.patch

New patch that includes many minor fixes (renaming, adding comments, etc.). The biggest change is that the AdminServer is started before a ZK server is created (this mimics the behavior of the current 4lw commands -- the CnxnFactory is created before the ZK server), and now an AdminServer is started for quorum members and not just standalone servers.
                
> Handle 4lws and monitoring on separate port
> -------------------------------------------
>
>                 Key: ZOOKEEPER-1346
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1346
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>            Reporter: Camille Fournier
>            Assignee: Skye Wanderman-Milne
>             Fix For: 3.5.0
>
>         Attachments: ZOOKEEPER-1346.2.patch, ZOOKEEPER-1346_jetty.patch, ZOOKEEPER-1346.patch
>
>
> Move the 4lws to their own port, off of the client port, and support them properly via long-lived sessions instead of polling. Deprecate the 4lw support on the client port. Will enable us to enhance the functionality of the commands via extended command syntax, address security concerns and fix bugs involving the socket close being received before all of the data on the client end.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira