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

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

GitHub user anmolnar opened a pull request:

    https://github.com/apache/zookeeper/pull/415

    ZOOKEEPER-2933: Added last/min/max proposal size JMX beans

    https://issues.apache.org/jira/browse/ZOOKEEPER-2933
    - Refactor proposal serialization logic to a common place (SerializeUtils),
    - Add JMX metric to monitor jute.maxbuffer setting
    - Add JMX metric to monitor min/max/last size of generated proposals
    - Unit tests

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/anmolnar/zookeeper ZOOKEEPER-2933

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zookeeper/pull/415.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #415
    
----
commit 67efc8553d80b374146aac07613eb3e217ba080f
Author: Andor Molnár <an...@cloudera.com>
Date:   2017-11-06T16:31:44Z

    ZOOKEEPER-2933: Added last/min/max proposal size JMX beans
    
    - Refactor proposal serialization logic to a common place,
    - Add JMX metric to monitor jute.maxbuffer setting
    - Add JMX metric to monitor min/max/last size of generated proposals

----


> 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 setting,
> 2. Add get last/min/max ProposalSize to LeaderBean which monitors the size of 
> the latest/min/max proposal.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to