[
https://issues.apache.org/jira/browse/ZOOKEEPER-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flavio Junqueira updated ZOOKEEPER-2398:
----------------------------------------
Fix Version/s: 3.5.3
3.6.0
> Config options should not be only available via system property
> ---------------------------------------------------------------
>
> Key: ZOOKEEPER-2398
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2398
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Jason Rosenberg
> Priority: Minor
> Fix For: 3.6.0, 3.5.3
>
>
> Some config options (such as enabling readonly mode) are only settable via a
> system property. This feels clunky, and makes it less seamless for testing,
> or for apps which embed a ZooKeeper inside a java container, etc.
> I ran into this issue specifically in the case of creating unit tests to test
> read-only mode client side behavior. In this case, I want to run multiple
> QuorumPeer's in the same jvm, and have some of them enabled for read-only and
> some not enabled. This is not possible with the current System.setProperty
> approach.
> In general, I question the need for using system properties for
> configuration, since it makes embedding a server within a dependency
> injection framework more difficult, and is in general less easy to integrate
> into generic deployment systems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
