You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Minwoo Kang (Jira)" <ji...@apache.org> on 2025/09/19 02:30:00 UTC

[jira] [Created] (ZOOKEEPER-4979) Provide Metric for Maximum Ephemeral Node Path Length per Session

Minwoo Kang created ZOOKEEPER-4979:
--------------------------------------

             Summary: Provide Metric for Maximum Ephemeral Node Path Length per Session
                 Key: ZOOKEEPER-4979
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4979
             Project: ZooKeeper
          Issue Type: Improvement
            Reporter: Minwoo Kang


h4. Background

Currently, ZooKeeper handles the deletion of ephemeral nodes on closeSession by processing a session-based delete transaction, rather than creating a separate delete transaction for each znode.
If a session with a large number of ephemeral nodes is closed, the resulting transaction can exceed the jute.maxbuffer limit, causing errors.
h4. Problem
 * When closing sessions with many ephemeral nodes, the delete transaction size may exceed {{{}jute.maxbuffer{}}}, resulting in "unreasonable length" errors and potential ZooKeeper failures.
 * ZooKeeper currently provides metrics for the number and size of ephemeral nodes, but does not provide metrics for the total path length of ephemeral nodes created by each session.
 * As a result, operators have difficulty estimating an appropriate value for {{jute.maxbuffer}} and cannot proactively monitor for related issues.

h4. Improvement Suggestion
 * Provide a metric for the total path length of ephemeral nodes created by each session.
 * It is not necessary to provide this information for all sessions; reporting only the session with the largest total path length would be sufficient.
 * This metric would help operators determine a reasonable value for jute.maxbuffer and prevent related failures.



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