hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: Tables Miss after Adding New Slave
Date Thu, 11 Mar 2010 15:52:19 GMT
No need to restart hbase.  Just start up pertinent services on added
node.  For example start datanode and then then start regionserver
daemons as follows:

> ${HADOOP_HOME}/bin/hadoop-daemon.sh start datanode
> ${HBASE_HOME}./bin/hbase-daemon.sh start regionserver


On Wed, Mar 10, 2010 at 10:28 PM,  <sallonchina@hotmail.com> wrote:
> Hi, Stack. I have another question:  what should I do if I want to add a new
> node to hadoop/hbase cluster as I described in previous letter. Is it OK
> that I configure the new node, add it into hadoop slaves and into hbase
> regionservers  and then restart Hadoop/Hbase? What else should I pay
> attention to? Thanks!
> Xianglong
> --------------------------------------------------
> From: "Stack" <stack@duboce.net>
> Sent: Wednesday, March 10, 2010 11:59 PM
> To: <hbase-user@hadoop.apache.org>
> Subject: Re: Tables Miss after Adding New Slave
>> 2010/3/10  <sallonchina@hotmail.com>:
>>> Hi, everyone. I set up a hadoop cluster with 3 nodes: one mater and two
>>> slaves. Recently I want to add a new node as a slave to it. After
>>> configuration, the HDFS and HBase work, however, I found some tables in
>>> HBase previously disappear. I browse hbase directory in HDFS and found
>>> directories of the missing tables. Does anyone encounter the same situations
>>> or is there someone can help me to recover these tables? thanks!
>> Perhaps the node carrying the .META. region -- the catalog table that
>> has table info -- was killed before it had time to flush its edits so
>> added table edits were lost?
>> You could playing with the ./bin/add_table.rb script.  See the head of
>> the script for how to use it.  This should restore your tables by
>> reading the content of the filesystem adding back the missing edits to
>> .META..
>> In future, be careful how you close down your cluster.  You could try
>> flushing .META. first before running shutdown by doing the following
>> in the shell:
>> hbase> flush ".META."
>> St.Ack

View raw message