You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Arshad Mohammad (JIRA)" <ji...@apache.org> on 2016/04/26 10:02:12 UTC
[jira] [Created] (ZOOKEEPER-2416) Remove Java System property usage
from ZooKeeper server code
Arshad Mohammad created ZOOKEEPER-2416:
------------------------------------------
Summary: Remove Java System property usage from ZooKeeper server code
Key: ZOOKEEPER-2416
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2416
Project: ZooKeeper
Issue Type: Improvement
Components: server
Reporter: Arshad Mohammad
Fix For: 3.5.3
Many ZooKeeper properties are used as Java System properties in the ZooKeeper code.
Some example:
{code}
public static int getSnapCount() {
String sc = System.getProperty("zookeeper.snapCount");
{code}
{code}
public int getGlobalOutstandingLimit() {
String sc = System.getProperty("zookeeper.globalOutstandingLimit");
{code}
Using ZooKeeper properties as Java system properties causes following problems
# Can not create two or more ZooKeeper Server in a single JVM with different properties for testing
# The properties initialization and validation is very much mixed with actual business logic which should not be the case.
ZOOKEEPER-2139 removed the ZooKeeper client side Java System properties so as part of this jira handling only ZooKeeper server side Java System properties to be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)