Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of meatforums@gmail.com
 designates 209.85.216.179 as permitted sender)
MIME-Version: 1.0
Date: Thu, 27 Oct 2011 09:43:48 -0700
Message-ID: 
 <CANN9sNogpPJ=1cRW5LL6J20pB=zS2kxMP04VaoOv=axM1yCb3Q@mail.gmail.com>
Subject: Monitoring question for a multi DC (active/standby) configuration
From: Anand Somani <meatforums@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=00163642711412f3fc04b04a7ad9

--00163642711412f3fc04b04a7ad9
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Have a requirement to do a multi dc low latency application. This will be
in an active/standby setup. So I am planning on using LOCAL_QUORUM for
writes. Now if there is a hard requirement of maximum loss of data (on a dc
destruction) to some minutes,

   - In cassandra what is the recommended approach to monitor the cluster
   so that I can find out when I am going to miss my SLA (of data loss)? Is
   this even possible?  Can this be monitored in cassandra (message dropped,
   or something) or has to be done outside?
   - I am also open to other suggestions, if there is a another way of
   doing active/standby with durability guarantees. Or is this not possible
   and I should use EACH_QUORUM

I found a few emails on active/standby, but nothing about monitoring, so if
this is already a discussed/solution suggested problem please forward the
link.

Thanks
Anand

--00163642711412f3fc04b04a7ad9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>Have a requirement to do a multi dc low latency application. Thi=
s will be in an active/standby setup. So I am planning on using LOCAL_QUORU=
M for writes. Now if there is a hard requirement of maximum loss of data (o=
n a dc destruction) to some minutes, <br>
<ul><li>In cassandra what is the recommended approach to monitor the cluste=
r so that I can find out when I am going to miss my SLA (of data loss)? Is =
this even possible?=A0 Can this be monitored in cassandra (message dropped,=
 or something) or has to be done outside? </li>
<li>I am also open to other suggestions, if there is a another way of doing=
 active/standby with durability guarantees. Or is this not possible and I s=
hould use EACH_QUORUM</li></ul>I found a few emails on active/standby, but =
nothing about monitoring, so if this is already a discussed/solution sugges=
ted problem please forward the link.<br>
<br>Thanks<br>Anand<br><br><br>

--00163642711412f3fc04b04a7ad9--