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-2933) Ability to monitor the jute.maxBuffer usage in real-time
Date Thu, 09 Nov 2017 13:24:00 GMT

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

ASF GitHub Bot commented on ZOOKEEPER-2933:

Github user anmolnar commented on the issue:

    @afine I've created 2 subtasks for the Jira as you suggested and changed this PR to refer
to the right one.

> Ability to monitor the jute.maxBuffer usage in real-time
> --------------------------------------------------------
>                 Key: ZOOKEEPER-2933
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2933
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: jute, server
>            Reporter: Andor Molnar
>            Assignee: Andor Molnar
>              Labels: buffer, buffer-length
>             Fix For: 3.5.4, 3.6.0
> This is related to jute.maxbuffer problems on the server side when Leader generates a
proposal that doesn't fit into Follower's Jute buffer causing the quorum to be broken.
> Proposed solution is to add the following new JMX Beans:
> 1. Add getJuteMaxBuffer to ZookeeperServerBean which monitors the current jute.maxbuffer
> 2. Add get last/min/max ProposalSize to LeaderBean which monitors the size of the latest/min/max

This message was sent by Atlassian JIRA

View raw message