Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Note on how zk has to be up and running to migrate/clean zk 

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1488005 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael Stack 2013-05-30 20:51:45 +00:00
parent 018ae9e0d5
commit 404cdce722
1 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
src/main/docbkx/upgrading.xml
View File

@ -94,8 +94,20 @@
<title>Cleaning zookeeper of old data</title>
<para>Clean zookeeper of all its content before you start 0.96.x (or 0.95.x). Here is how:
<programlisting>$ ./bin/hbase clean</programlisting>
This will printout usage. Run the following to clean zookeeper in particular
This will printout usage.</para>
<para>To 'clean' ZooKeeper, it needs to be running. But you don't want the cluster running
because the cluster will then register its entities in ZooKeeper and as a precaution,
our clean script will not run if there are registered masters and regionservers with
registered znodes present. So, make sure all servers are down but for zookeeper. If
zookeeper is managed by HBase, a commmon-configuration, then you will need to start
zookeeper only:
<programlisting>$ ./hbase/bin/hbase-daemons.sh --config /home/stack/conf-hbase start zookeeper</programlisting>
If zookeeper is managed independently of HBase, make sure it is up.
Now run the following to clean zookeeper in particular
<programlisting>$ ./bin/hbase clean --cleanZk</programlisting>
It may complain that there are still registered regionserver znodes present in zookeeper.
If so, ensure they are indeed down. Then wait a few tens of seconds and they should
disappear.
</para>
<para>This is what you will see if zookeeper has old data in it: the Master won't start with
an exception like the following