[ZOOKEEPER-2394] Many ZooKeeper properties are not configurable in zoo.cfg

• Type: Improvement
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 3.7.0, 3.5.9
• Component/s: server
• Assignee: Mohammad Arshad
• Reporter: Mohammad Arshad
• Created: 21/Mar/16 09:38
• Updated: 30/Apr/20 16:22

Description

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.

1. follower.nodelay
2. leader.nodelay
3. readonlymode.enabled
4. jute.maxbuffer
5. znode.container.checkIntervalMs
6. znode.container.maxPerMinute

This jira targets to make these properties configurable in zoo.cfg as well.

Issue Links

• contains: ZOOKEEPER-2398 Config options should not be only available via system property
• is related to: ZOOKEEPER-2195 fsync.warningthresholdms in zoo.cfg not working