It seems stop-hbase.sh only stops master/backup masters and zookeepers. So, according to my understanding, region servers shall shutdown itself since it can't find either master or zookeeper.
But, I made a recent experimentation on our hbase cluster. After 2 days of mater/zookeeper shutdown, the region servers are still alive. I am not sure whether it is the problem in hbase release or our own problem since our version is a heavy patched one. Then, can I perform hbase cluster in following way? 1. stop master 2. stop master backups 3. stop zookeepers 4. stop region servers The only difference is step #4. If I manually stop down RS, will it affect data integrity? If not, then I can safely performed the steps to shutdown the cluster. Thanks Weihua 2011/7/13 Ted Yu <[email protected]>: > For #2: > > bin/stop-hbase.sh > check that master and region servers are down > ... > bin/start-hbase.sh > > On Tue, Jul 12, 2011 at 11:29 PM, Weihua JIANG <[email protected]>wrote: > >> Hi all, >> >> I am using HBase 0.90+HBASE-3789 and I want to know how to restart the >> cluster safely. >> >> Basically, there are two kinds of restarts: >> 1. Keep the HBase cluster working while restarting the whole cluster. >> 2. Stop-the-world cluster restart which only ensure data safety. >> >> From my understanding, graceful_stop.sh and rolling restart is used >> for kind #1. But, HBASE-3789 said it broke rolling restart. So, can >> anyone tell me what it broke and how to fix it to make rolling restart >> work? >> >> And, I can't find document about the kind #2 stop-the-world restart. >> Can any one point me the how-to document about it? >> >> Thanks >> Weihua >> >
