You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "cheng (Jira)" <ji...@apache.org> on 2025/04/15 07:19:00 UTC

[jira] [Created] (ZOOKEEPER-4916) Zookeeper's jute.maxbuffer issue causes cluster exceptions, how to raise alerts through monitoring

cheng created ZOOKEEPER-4916:
--------------------------------

             Summary: Zookeeper's jute.maxbuffer issue causes cluster exceptions, how to raise alerts through monitoring
                 Key: ZOOKEEPER-4916
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4916
             Project: ZooKeeper
          Issue Type: Improvement
          Components: jute
    Affects Versions: 3.9.3
            Reporter: cheng


From the implementation of ZooKeeper, deleting temporary nodes during closeSession is a deletion transaction operation based on the session, rather than creating a separate deletion transaction for each znode node. That's why there is an unreasonable length issue. But how to monitor the size of transactions? Does the official have any corresponding monitoring items or solutions to solve this problem



--
This message was sent by Atlassian Jira
(v8.20.10#820010)