zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Han (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-2394) Many ZooKeeper properties are not configurable in zoo.cfg
Date Mon, 13 Mar 2017 16:22:13 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Han updated ZOOKEEPER-2394:
-----------------------------------
    Fix Version/s:     (was: 3.5.3)
                   3.6.0
                   3.5.4

> 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: Mohammad Arshad
>            Assignee: Mohammad Arshad
>             Fix For: 3.5.4, 3.6.0
>
>         Attachments: ZOOKEEPER-2394-01.patch, ZOOKEEPER-2394-02.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
> # leader.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.15#6346)

Mime
View raw message