[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cassandra-user
Subject:    Re: I am looking for cross data center HA solution
From:       Santal Li <santal.li () gmail ! com>
Date:       2009-10-14 13:38:24
Message-ID: f91bc4fd0910140638n4d653b49m16931277edef4740 () mail ! gmail ! com
[Download RAW message or body]

Thanks for your quickly response, and also excellent job on this project.

For such kind of HA, we need do 2 way data sync. After failover to DC2, the
data change will be replicate to DC1 again, we had done same work with our
cross DC file system HA solution, so I prefer to this solution at beginning.
:)

Thanks for your suggestion, I think you are right, you guys do very good job
on the replication & failover with Cassandra, it was one of the best part of
this project. So let me try it. Thanks again.


Regards
-Santal



2009/10/14 Jonathan Ellis <jbellis@gmail.com>

> On Wed, Oct 14, 2009 at 1:53 AM, Santal Li <santal.li@gmail.com> wrote:
> > There was another way for cross data center HA,  how about add some kind
> of
> > action hook, which can catch all the Cassandra.Iface function call(insert
> ,
> > batch_insert , remove ...) , then send the call to another Cassandra
> cluster
> > in remote data center? If so, there will be 1 Cassandra clusters in each
> 2
> > data centers, and have a extra application replicate data between the two
> > cluster. I prefer with this solution, because it looks more simple and
> > uncoupled 2 data center, BTW, from the source code, it looks was not very
> > hard to add a hook for this purpose , how do you think about it? is there
> > anyone meet the same requirements,  can you please give me some
> suggestion.
>
> That works fine, until you actually have a failure.  Then how do you
> re-sync your clusters after you've done some writes in the second DC?
> The advantage to letting Cassandra handle replication + failover is
> all the hard parts are done already. :)
>
> -Jonathan
>

[Attachment #3 (text/html)]

Thanks for your quickly response, and also excellent job on this project.<br><br>For \
such kind of HA, we need do 2 way data sync. After failover to DC2, the data change \
will be replicate to DC1 again, we had done same work with our cross DC file system \
HA solution, so I prefer to this solution at beginning. :) <br> <br>Thanks for your \
suggestion, I think you are right, you guys do very good job on the replication &amp; \
failover with Cassandra, it was one of the best part of this project. So let me try \
                it. Thanks again.<br><br><br>Regards<br>
-Santal<br><br><br><br><div class="gmail_quote">2009/10/14 Jonathan Ellis <span \
dir="ltr">&lt;<a href="mailto:jbellis@gmail.com">jbellis@gmail.com</a>&gt;</span><br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> <div class="im">On Wed, Oct 14, 2009 at 1:53 AM, \
Santal Li &lt;<a href="http://santal.li" target="_blank">santal.li</a>@<a \
href="http://gmail.com" target="_blank">gmail.com</a>&gt; wrote:<br> </div><div \
class="im">&gt; There was another way for cross data center HA,  how about add some \
kind of<br> &gt; action hook, which can catch all the Cassandra.Iface function \
call(insert ,<br> &gt; batch_insert , remove ...) , then send the call to another \
Cassandra cluster<br> &gt; in remote data center? If so, there will be 1 Cassandra \
clusters in each 2<br> &gt; data centers, and have a extra application replicate data \
between the two<br> &gt; cluster. I prefer with this solution, because it looks more \
simple and<br> &gt; uncoupled 2 data center, BTW, from the source code, it looks was \
not very<br> &gt; hard to add a hook for this purpose , how do you think about it? is \
there<br> &gt; anyone meet the same requirements,  can you please give me some \
suggestion.<br> <br>
</div>That works fine, until you actually have a failure.  Then how do you<br>
re-sync your clusters after you&#39;ve done some writes in the second DC?<br>
The advantage to letting Cassandra handle replication + failover is<br>
all the hard parts are done already. :)<br>
<font color="#888888"><br>
-Jonathan<br>
</font></blockquote></div><br>



[prev in list] [next in list] [prev in thread] [next in thread]