[
https://issues.apache.org/jira/browse/ZOOKEEPER-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arshad Mohammad updated ZOOKEEPER-2394:
---------------------------------------
Attachment: ZOOKEEPER-2394-01.patch
Submitting the fix.
# Boolean.getBoolean("readonlymode.enabled"), implicitly indicates that the
default value for readonlymode.enabled is false. Used readonlymode.enabled
value false
# jute.maxbuffer is used both at client side as well as server side. At client
side there is no zoo.cfg like configuration file but changed jute.maxbuffer to
zookeeper.jute.maxbuffer to make it same at sever and client side. anyway
jute.maxbuffer as a system property will work fine
# Container znode type was introduced in 3.5.1 so changed document accordingly
> Many ZooKeeper properties are not configurable in zoo.cfg
> ---------------------------------------------------------
>
> Key: ZOOKEEPER-2394
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2394
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Reporter: Arshad Mohammad
> Assignee: Arshad Mohammad
> Fix For: 3.5.2
>
> Attachments: ZOOKEEPER-2394-01.patch
>
>
> Many ZooKeeper properties are not configurable in zoo.cfg. If configured in
> zoo.cfg, {{QuorumPeerConfig}} parse logic will pre append "zookeeper" which
> is not the same property used in code. So a property with a name {{abc.xyz}}
> becomes {{zookeeper.abc.xyz}}
> Bellow are properties which can not configured in zoo.cfg, can only be
> configured using java system properties.
> # follower.nodelay
> # readonlymode.enabled
> # jute.maxbuffer
> # znode.container.checkIntervalMs
> # znode.container.maxPerMinute
> This jira targets to make these properties configurable in zoo.cfg as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
