Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 75748 invoked from network); 8 Dec 2009 19:25:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Dec 2009 19:25:14 -0000 Received: (qmail 33726 invoked by uid 500); 8 Dec 2009 19:25:13 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 33680 invoked by uid 500); 8 Dec 2009 19:25:13 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 33671 invoked by uid 99); 8 Dec 2009 19:25:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Dec 2009 19:25:12 +0000 X-ASF-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of vijay2win@gmail.com designates 209.85.222.174 as permitted sender) Received: from [209.85.222.174] (HELO mail-pz0-f174.google.com) (209.85.222.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Dec 2009 19:25:10 +0000 Received: by pzk4 with SMTP id 4so4932493pzk.32 for ; Tue, 08 Dec 2009 11:24:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=P2xTnayJ7HAMNV2+hnfa8d4jvEsJ1v8Lgeiq2ae7Ths=; b=Dt0KkXNEYCbdPq2orsNUfF96jyHVkShdGoxbfoxg4hEwnYxwEGVXVSBvUmnC1xuKDe njJw4HVR2zBogpewdShdWsgeG1HepXOy6bq0zWP9fsQyRmfCJ7HUSNCq5AT6fH1/sgtW W67V0Arkt8ebwsMBFAcQLSMfLYdCe8V+KSxz8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=cmQ1i7Fpjx5CxvaQu9s29e8MZz9e2WOegEkPD0ZmL2E3MSnBhBRj464hKG9RaqldZ0 4653khuaNYyobSgOnM0q7IIjicglYjvqck+KwdfajqmQlVrVJCJbd5eNnZeonksgMwUc A4jrM857CXnk1he+GnT78KbTN8sRuXC2YXReQ= MIME-Version: 1.0 Received: by 10.142.74.7 with SMTP id w7mr937962wfa.149.1260300290097; Tue, 08 Dec 2009 11:24:50 -0800 (PST) In-Reply-To: References: <87a60d5b0912080521r5d124df6wa7ffae90940b74b3@mail.gmail.com> From: Vijay Date: Tue, 8 Dec 2009 11:24:30 -0800 Message-ID: <9b40bc2a0912081124s12eeabf0m71df2656771cd676@mail.gmail.com> Subject: Re: Configuring Cassandra To: cassandra-user@incubator.apache.org Content-Type: multipart/alternative; boundary=001636e1fb261a02ae047a3c87c2 --001636e1fb261a02ae047a3c87c2 Content-Type: text/plain; charset=UTF-8 a) Multiple DCs: Can I control that each key should store in each and every data center? If it is possible, an example configuration will be helpful. you cannot.... and if you did the ring will break... consider Cassandra in multiple DC as one big Ring..... We use Cassandra to have copies of all data in all the DC's Regards, On Tue, Dec 8, 2009 at 5:56 AM, Mark Robson wrote: > I'm not an expert in Cassandra yet but I do know a little, here are some > (attempted) answers: > > 2009/12/8 Rakesh Sharma > > b) Apart from nodeprobe and Jconsole is there any other node management >> tool? >> > > You can use any JMX application, apparently, to monitor it. This could be > done e.g. via a command line script (assuming there is a convenient JMX CLI) > and then hooked into your monitoring. I'd look there first. I have not tried > this (yet). > > d) Can I control where a node will be added in the ring? How is it decided? >> Primarily, I want to understand how the hot-spots can be handled? >> > > You can pick the token manually before first startup; it gets read from the > config file. > > Detecting hot-spots is not easy. If you use the OrderedPartitioner, then > hot spots tend to occur where you put all your keys. The fix is to spread > out your keys, or bunch up your nodes, but if you use time-based keys or > similar, your key distribution will change over time so you can't win that > way. > > Nodes can be decommissioned now (as of 0.5 I think) with the nodeprobe > decommission command. You can then stop the node, clear all its data and > re-bootstrap it with a different token. This is not an automatic or > particularly fast or convenient process. > > >> e) How a node data backup should be taken such that reads and writes at >> that time are not effected (read or write locks)? Any tool/utility that can >> be used? >> > > The nodeprobe snapshot can take a snapshot of an individual node. You can > of course schedule these to happen at (about) the same time. > >> >> f) Can I take backups from each node and merge them on a single node? Or >> it's not at all required? >> > > Dunno, sounds nontrivial. > > Mark > --001636e1fb261a02ae047a3c87c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable a) Multiple DCs: Can I control that each key should store in each and every data center? If it is possible, an example configuration will be helpful.
=C2=A0=C2=A0=C2=A0 you= cannot.... and if you did the ring will break... consider Cassandra in mul= tiple DC as one big Ring..... We use Cassandra to have copies of all data i= n all the DC's

Regards,
</VJ>




On Tue, Dec 8, 2009 at 5:56 AM, Mark Rob= son <markxr@gmail.= com> wrote:
I'm not an expert in Cassandra yet but I do = know a little, here are some (attempted) answers:

2009/12/8 Rakesh S= harma <rakrma@gmail.com>

b) Apart from nodeprobe and Jconsole is there any = other node management tool?

You can use any JMX application, apparently, to= monitor it. This could be done e.g. via a command line script (assuming th= ere is a convenient JMX CLI) and then hooked into your monitoring. I'd = look there first. I have not tried this (yet).

d) Can I control where a node will be added in the ring? How is = it decided? Primarily, I want to understand how the hot-spots can be handle= d?

You can pick the token manually before first st= artup; it gets read from the config file.

Detecting hot-spots is not= easy. If you use the OrderedPartitioner, then hot spots tend to occur wher= e you put all your keys. The fix is to spread out your keys, or bunch up yo= ur nodes, but if you use time-based keys or similar, your key distribution = will change over time so you can't win that way.

Nodes can be decommissioned now (as of 0.5 I think) with the nodeprobe = decommission command. You can then stop the node, clear all its data and re= -bootstrap it with a different token. This is not an automatic or particula= rly fast or convenient process.
=C2=A0
e) How a node data backup should be taken such that reads and = writes at that time are not effected (read or write locks)? Any tool/utilit= y that can be used?

The nodeprobe snapshot can take a snapshot of a= n individual node. You can of course schedule these to happen at (about) th= e same time.=C2=A0

f) Can I take backups from each node and merge them on a single node? O= r it's not at all required?

= Dunno, sounds nontrivial.

Mark

--001636e1fb261a02ae047a3c87c2--