[
https://issues.apache.org/jira/browse/ZOOKEEPER-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468645#comment-13468645
]
Patrick Hunt commented on ZOOKEEPER-1346:
-----------------------------------------
Sounds like a great idea to me. I've seen a number of issues now with users
experiencing this problem. Also the fact that some users don't like that the
monitoring port is the same as the session port. They'd like to
segregate/firewall this off (the 4lw from user of the zk service itself).
If we do add this it would be good if there was a way to include it optionally.
Some projects integrate ZK into their system (think embedded zk, e.g. hbase)
and have their own container requirements. Similarly some users may not want to
include jetty dependencies/runtime for whatever reason.
Given the rest of the hadoop ecosystem typically has similar functionality
(jetty based http/s interfaces) it doesn't seem like we're going to far afield
here.
> 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: Camille Fournier
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1346_jetty.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
