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

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]> wrote:
> 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

Hi Mohammad:

The current HBase replication (as far as I understand) is designed to
replicate data from one data center to another data center. The client
application has no knowledge of the zookeeper ensemble in the slave cluster
and therefore, it cannot switch to the slave cluster in case of a system
failure. You might want to implement a smart client can switch to the slave
cluster when it "detects" a failure. Be aware of the data might not
immediately available to the slave cluster (i.e. the master cluster might
have the most up-to-date data than the slave cluster even you configured
the replication)

HTH,

Jerry

On Fri, Jun 22, 2012 at 5:18 PM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:

> 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
>

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]> wrote:
> 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]> wrote:
>> 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

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.

Regards,
    Mohammad Tariq
On Sat, Jun 23, 2012 at 3:35 AM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
> 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]> wrote:
>> 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]> wrote:
>>> 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

Hi All,

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
running.

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
in TBs)?
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
master)

Need Advice.
Thanks,

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.
>
> Regards,
>     Mohammad Tariq
>
>
> On Sat, Jun 23, 2012 at 3:35 AM, Mohammad Tariq <[EMAIL PROTECTED]>
> wrote:
> > 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]>
> wrote:
> >> 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]>
> wrote:
> >>> 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
>

--
Alok Kumar

better you keep the data replication on the both cluster and do some
setting so that it will keep on monitoring the availability of the namenode
the script for that is available at github, which will monitor the namenode
if it goes down then next request should be redirected to the other running
cluster back and forth.

On Sat, Jun 23, 2012 at 5:02 PM, Alok Kumar <[EMAIL PROTECTED]> wrote:

> Hi All,
>
> 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
> running.
>
> 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
> in TBs)?
> 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
> master)
>
> Need Advice.
> Thanks,
>
> 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.
> >
> > Regards,
> >     Mohammad Tariq
> >
> >
> > On Sat, Jun 23, 2012 at 3:35 AM, Mohammad Tariq <[EMAIL PROTECTED]>
> > wrote:
> > > 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]>
> > wrote:
> > >> 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]>
> > wrote:
> > >>> 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
> >
>
>
>
> --
> Alok Kumar
>

--
∞
Shashwat Shriparv

Are clients local to slave DC able to read data from HBase slave when
replicating data from one DC to remote DC? If not then is there a way to
design such a thing where clients are able to actively read/write from both
DCs?