We are going to setup two clusters(Master-Slave) for disaster recovery.
If Custer1 goes down.. HBase client will connect to Slave Custer2, then I
can use copyTable command to update Cluster1 tables when it is up again
But in case, I loose all my data on Cluster1 !!
What is the best/quickest way to bring data from Cluster2(data size will be
I will be able to recreate all my tables on Cluster1 with schema stored but
using copyTable for >1000 tables does not sound good.
Master Cluster : 6-7 nodes (say)
Slave Cluster : 2 nodes (with larger disk sizes for data replication from
On Sat, Jun 23, 2012 at 3:41 AM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
> Hello Jerry,
> Thank you so much for the valuable reply..It makes perfect
> sense..I think this topic needs some labor and testing from my side.
> Mohammad Tariq
> On Sat, Jun 23, 2012 at 3:35 AM, Mohammad Tariq <[EMAIL PROTECTED]>
> > Thanks a lot for the quick response J-D..Could you please give me some
> > direction on how to do this at the application level??I am not able to
> > figure it out.(Please pardon my ignorance).
> > Regards,
> > Mohammad Tariq
> > On Sat, Jun 23, 2012 at 2:52 AM, Jean-Daniel Cryans <[EMAIL PROTECTED]>
> >> For the moment each cluster is viewed as a completely different
> >> entity, HBase doesn't offer a layer on top of it all (much like
> >> MySQL). Thus the "taking it's place" part needs to be solved at the
> >> application level.
> >> Hope this helps,
> >> J-D
> >> On Fri, Jun 22, 2012 at 2:18 PM, Mohammad Tariq <[EMAIL PROTECTED]>
> >>> Hello list,
> >>> I was going through the Hbase Replication documentation(at
> >>> http://hbase.apache.org/replication.html) to get myself clear with the
> >>> concepts..One thing which I could not find is that whether it is
> >>> possible to configure the replication in such a way that if my master
> >>> cluster goes down the slave cluster will automatically take its
> >>> place..Need some advice/comments from the experts.Many thanks.
> >>> Regards,
> >>> Mohammad Tariq