You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2012/11/30 05:47:57 UTC
[jira] [Created] (HBASE-7244) Provide a command or argument to
startup, that formats znodes if provided
Harsh J created HBASE-7244:
------------------------------
Summary: Provide a command or argument to startup, that formats znodes if provided
Key: HBASE-7244
URL: https://issues.apache.org/jira/browse/HBASE-7244
Project: HBase
Issue Type: New Feature
Components: Zookeeper
Affects Versions: 0.94.0
Reporter: Harsh J
Priority: Minor
Many a times I've had to, and have seen instructions being thrown, to stop cluster, clear out ZK and restart.
While this is only a quick (and painful to master) fix, it is certainly nifty to some smaller cluster users but the process is far too long, roughly:
1. Stop HBase
2. Start zkCli.sh and connect to the right quorum
3. Find and ensure the HBase parent znode from the configs (/hbase only by default)
4. Run an "rmr /hbase" in the zkCli.sh shell, or manually delete each znode if on a lower version of ZK.
5. Quit zkCli.sh and start HBase again
Perhaps it may be useful, if the start-hbase.sh itself accepted a formatZK parameter. Such that, when you do a {{start-hbase.sh -formatZK}}, it does steps 2-4 automatically for you.
For safety, we could make the formatter code ensure that no HBase instance is actually active, and skip the format process if it is. Similar to a HDFS NameNode's format, which would disallow if the name directories are locked.
Would this be a useful addition for administrators? Bigtop too can provide a service subcommand that could do this.
--
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
[jira] [Commented] (HBASE-7244) Provide a command or argument to
startup, that formats znodes if provided
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507098#comment-13507098 ]
stack commented on HBASE-7244:
------------------------------
Sounds good to me Harsh.
> Provide a command or argument to startup, that formats znodes if provided
> -------------------------------------------------------------------------
>
> Key: HBASE-7244
> URL: https://issues.apache.org/jira/browse/HBASE-7244
> Project: HBase
> Issue Type: New Feature
> Components: Zookeeper
> Affects Versions: 0.94.0
> Reporter: Harsh J
> Priority: Minor
>
> Many a times I've had to, and have seen instructions being thrown, to stop cluster, clear out ZK and restart.
> While this is only a quick (and painful to master) fix, it is certainly nifty to some smaller cluster users but the process is far too long, roughly:
> 1. Stop HBase
> 2. Start zkCli.sh and connect to the right quorum
> 3. Find and ensure the HBase parent znode from the configs (/hbase only by default)
> 4. Run an "rmr /hbase" in the zkCli.sh shell, or manually delete each znode if on a lower version of ZK.
> 5. Quit zkCli.sh and start HBase again
> Perhaps it may be useful, if the start-hbase.sh itself accepted a formatZK parameter. Such that, when you do a {{start-hbase.sh -formatZK}}, it does steps 2-4 automatically for you.
> For safety, we could make the formatter code ensure that no HBase instance is actually active, and skip the format process if it is. Similar to a HDFS NameNode's format, which would disallow if the name directories are locked.
> Would this be a useful addition for administrators? Bigtop too can provide a service subcommand that could do this.
--
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