You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "david babits (JIRA)" <ji...@apache.org> on 2013/05/25 05:12:21 UTC
[jira] [Commented] (ZOOKEEPER-279) Allow specialization of quorum
config parsing (e.g. variable expansion in zoo.cfg)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666940#comment-13666940 ]
david babits commented on ZOOKEEPER-279:
----------------------------------------
can somebody confirm whether this feature is available in zookeeper-3.4.5, I can't seem to see it implemented looking at source code in org.apache.zookeeper.server.quorum.QuorumPeerConfig
Thanks.
http://grepcode.com/file/repository.cloudera.com/content/repositories/releases/org.apache.zookeeper/zookeeper/3.4.5-cdh4.2.0/org/apache/zookeeper/server/quorum/QuorumPeerConfig.java#QuorumPeerConfig
> Allow specialization of quorum config parsing (e.g. variable expansion in zoo.cfg)
> ----------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-279
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-279
> Project: ZooKeeper
> Issue Type: Improvement
> Affects Versions: 3.1.0
> Reporter: Nitay Joffe
> Assignee: Jean-Daniel Cryans
> Priority: Minor
> Fix For: 3.1.1, 3.2.0
>
> Attachments: HBaseQPC.java, zookeeper-279.patch, zookeeper-279.patch
>
>
> We would like to define certain parts of ZooKeeper's configuration using variables that get substituted. For example, we want the ZooKeeper quorum to be able to use a dataDir configured per user. In other words, something like:
> tickTime=2000
> dataDir=/tmp/zookeeper-${user.name}
> clientPort=2181
> initLimit=5
> syncLimit=2
> server.1=zoo1:2888:3888
> server.2=zoo2:2888:3888
> server.3=zoo3:2888:3888
> I think Java already has a system for configuration that allows something like this using Properties?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira