[
https://issues.apache.org/jira/browse/BOOKKEEPER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439432#comment-13439432
]
Sijie Guo commented on BOOKKEEPER-300:
--------------------------------------
{quote}
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?
{quote}
BookieShell is added for BookkKeeper, which is similar as HedwigConsole added
for Hedwig. It is designed to put utilities for admin guys to operate/admin the
cluster. I think it is OK to put utilities for administration in it.
I don't have strong feel on it. But I think putting utilities for
administration together would help maintenance.
> 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
