[
https://issues.apache.org/jira/browse/NIFI-9082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405429#comment-17405429
]
ASF subversion and git services commented on NIFI-9082:
-------------------------------------------------------
Commit 0cf09840eabd6131be8a9a928c1b2e7df03eb0ee in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0cf0984 ]
NIFI-9082 Add nifi.zookeeper.jute.maxbuffer property (#5335)
* NIFI-9082 Added nifi.zookeeper.jute.maxbuffer property
- Updated ZooKeeperStateProvider to check jute.maxbuffer instead of hard-coded
number
- Updated internal ZooKeeperClientConfig class to include new juteMaxBuffer
property
* NIFI-9082 Updated jute.maxbuffer documentation and added hexadecimal
representation
- Renamed DefaultWatcher to NoOpWatcher
- Removed unnecessary validateDataSize() from createNode()
> ZooKeeperStateProvider should use jute.maxbuffer property
> ---------------------------------------------------------
>
> Key: NIFI-9082
> URL: https://issues.apache.org/jira/browse/NIFI-9082
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The {{ZooKeeperStateProvider}} includes a hard-coded limitation on the
> maximum state size of 1 MB. This is the default maximum size allowed for
> ZooKeeper nodes, but the value can be changed using the
> [jute.maxbuffer|http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#Unsafe+Options]
> property on both the client and server. The default value should be
> sufficient for the majority of use cases, but the {{ZooKeeperStateProvider}}
> should use this property to check the maximum state size instead of the
> hard-coded limit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
