Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of s5alye@gmail.com designates
 209.85.214.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=fcPTi0hYLvInPO/qrHZC+Iz1lDt0NfYV+PTvNIQKtEtu0AQr7VXInP+HAVeQO7VAMQ
         jEI6IXa/bdFk30N5EYg+EIiXPkTlELSn4EuScYuYkfUzVAtX2LUdc1pNeFr8oDrB2qxS
         QbSB32LhB6jBw4NPLhxyGIf2ej2nKyWB12bhM=
MIME-Version: 1.0
Date: Tue, 15 Feb 2011 15:45:16 -0500
Message-ID: <AANLkTinGK4tzJ+O0vaDzE5hHLjpKUH-x7SUFGrGk+zKE@mail.gmail.com>
Subject: Coordinator node
From: A J <s5alye@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001636c931e4e2118c049c583d4f

--001636c931e4e2118c049c583d4f
Content-Type: text/plain; charset=ISO-8859-1

>From my reading it seems like the node that the client connects to becomes
the coordinator node. Questions:

1. Is it true that the write first happens on the coordinator node and then
the coordinator node propagates it to the right primary node and the
replicas ? In other words if I have a 2G write, would the 2G be transferred
first to the coordinator node or is it just a witness and just waits for the
transfer to happen directly between the client and required right nodes ?

2. How do you load-balance between the different nodes to give all equal
chance to become co-ordinator node ? Does the client need a sort of
round-robin DNS balancer ? if so, what if some of the nodes drop off. How to
inform the DNS balancer  ?
Or do I need a proper load balancer in front that looks at the traffic on
each node and accordingly selects a co-ordinator node ? What is more
pervalent ?

Thanks.

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

>From my reading it seems like the node that the client connects to becomes =
the coordinator node. Questions:<div><br></div><div>1. Is it true that the =
write first happens on the coordinator node and then the coordinator node=
=A0propagates=A0it to the right primary node and the replicas ? In other wo=
rds if I have a 2G write, would the 2G be transferred first to the coordina=
tor node or is it just a witness and just waits for the transfer to happen =
directly between the client and required right nodes ?</div>
<div><br></div><div>2. How do you load-balance between the different nodes =
to give all equal chance to become co-ordinator node ? Does the client need=
 a sort of round-robin DNS balancer ? if so, what if some of the nodes drop=
 off. How to inform the DNS balancer =A0?</div>
<div>Or do I need a proper load balancer in front that looks at the traffic=
 on each node and accordingly selects a co-ordinator node ? What is more pe=
rvalent ?</div><div><br></div><div>Thanks.</div><div><br></div><div><br>
</div>

--001636c931e4e2118c049c583d4f--