[
https://issues.apache.org/jira/browse/BOOKKEEPER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439272#comment-13439272
]
Rakesh R commented on BOOKKEEPER-300:
-------------------------------------
@Sijie
bq.BTW, for Bookie format, it would better to put it in BookieShell to put all
bookie commands together.
Thanks Sijie for the suggestion. I'm having following doubts about the
BookieShell, would be great if you give more on this.
- BookieShell javadoc is saying "Bookie Shell to read/check bookie files."
- Also, one more I've observed is, presently the commands in the shell are
like: readledger, readlog, readjournal etc. I feel, all these are having
readonly behaviours. But the format command is a kind of write permission. Are
we designed the BookieShell to keep only readonly cmds?
Is it ok to keep the 'format' command in the shell. Any thoughts? If yes, it
would be good to look at and modify/update the javadocs also while creating the
format patch. Thanks
> Create Bookie format command
> ----------------------------
>
> Key: BOOKKEEPER-300
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-300
> Project: Bookkeeper
> Issue Type: New Feature
> Components: bookkeeper-server
> Affects Versions: 4.1.0
> Reporter: Rakesh R
> Attachments: BOOKKEEPER-300.patch, BOOKKEEPER-300.patch
>
>
> Provide a bookie format command. Then the admin would just have to run the
> command on each machine, which will prepare the bookie env
> +Zookeeper paths (znodes):+
> - ledger's root path
> - bookie's available path
> +Directories:+
> - Journal directories
> - Ledger directories
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
