[
https://issues.apache.org/jira/browse/BOOKKEEPER-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15729066#comment-15729066
]
ASF GitHub Bot commented on BOOKKEEPER-966:
-------------------------------------------
Github user jiazhai commented on the issue:
https://github.com/apache/bookkeeper/pull/75
@eolivelli That idea is great. How about open another new issue to tracking
this requirement?
> change the bookieServer cmdline to make conf-file and option co-exist
> ---------------------------------------------------------------------
>
> Key: BOOKKEEPER-966
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-966
> Project: Bookkeeper
> Issue Type: Improvement
> Reporter: Jia Zhai
> Assignee: Jia Zhai
>
> Currently, when using bookieServer cmdline to start a bookie, you will either
> give it a cofiguration file by "-c booke.conf"; or add some options like
> "<bookie_port> <zk_servers> <journal_dir> <ledger_dir [ledger_dir]>" in a fix
> sequential.
> It may not satisfy some of the requirement. So changed it to be co-exist for
> configuration file and options.
> By this change, it will first use settings in configuration file; and then
> use options to overwrite some of the settings, if there are some options
> provided.
> Here is an example after this change:
> BookieServer -c bookie.conf -z localhost:2181 -m /bookkeeper/ledgers -p 3181
> -j /mnt/journal -l "/mnt/ledger1 /mnt/ledger2 /mnt/ledger3”
> Here, in this command:
> -z is for “Zookeeper client instance”;
> -m is for "Zookeeper ledgers root path for bookies";
> -p is for "bookie service port exported";
> -j is for "bookie journal directory";
> -l is for "bookie ledgers directories".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
