zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2980) Backport ZOOKEEPER-2939 Deal with maxbuffer as it relates to proposals
Date Thu, 15 Feb 2018 21:59:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366319#comment-16366319
] 

ASF GitHub Bot commented on ZOOKEEPER-2980:
-------------------------------------------

Github user afine commented on the issue:

    https://github.com/apache/zookeeper/pull/462
  
    The patch looks good. I'm just wondering why we need this in 3.4. As I believe we generally
try not to add features to that branch at this point that don't improve security or stability.


> Backport ZOOKEEPER-2939 Deal with maxbuffer as it relates to proposals
> ----------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2980
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2980
>             Project: ZooKeeper
>          Issue Type: Sub-task
>          Components: server
>            Reporter: Andor Molnar
>            Assignee: Andor Molnar
>            Priority: Major
>             Fix For: 3.4.12
>
>
> Backport ZOOKEEPER-2939 to branch-3.4.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message