Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D5BD1950F for ; Fri, 10 Feb 2012 09:46:57 +0000 (UTC) Received: (qmail 29576 invoked by uid 500); 10 Feb 2012 09:46:49 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 28542 invoked by uid 500); 10 Feb 2012 09:46:19 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 28512 invoked by uid 99); 10 Feb 2012 09:46:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2012 09:46:14 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a46.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2012 09:46:07 +0000 Received: from homiemail-a46.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a46.g.dreamhost.com (Postfix) with ESMTP id 1E5DC3E405C for ; Fri, 10 Feb 2012 01:45:44 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=thelastpickle.com; h=from :mime-version:content-type:subject:date:in-reply-to:to :references:message-id; q=dns; s=thelastpickle.com; b=ssEg8pL1vg cEqZ0HXC6hUV2HxbSzMl+wTEfWKyez3FOMVE1HFWNIUrMUfoTMKBnrvuwfnBNnO0 7uuOreRfwsqUGWJXCNtNYAEkSgiPXtRg8Dn0Y01f0LP+8/D7JqhqXLK/2iLEwEhA jmmp4v73NyyJnqhu1zEbENSZpttYDWb2I= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :mime-version:content-type:subject:date:in-reply-to:to :references:message-id; s=thelastpickle.com; bh=6V5GlNW67qE416vm fY6eHHdhlnU=; b=HVQq3udQ90xeFYcC26QxOo9JJPtjKW5WxVfzLAxLPxV3v+Nk Oa6OLKda9Uv28i6Db+LbF9VKCFkU0WPV1o1q2qK1+barIQrmKuyyQBij1NcWFVG7 XqwiRaf77R3SItdeCz+XRkwSTHVcmGt5Hv+Wbxy3U//Or9QGK3P5hjMTnyA= Received: from [172.16.1.3] (125-236-193-159.adsl.xtra.co.nz [125.236.193.159]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a46.g.dreamhost.com (Postfix) with ESMTPSA id CC7BD3E405B for ; Fri, 10 Feb 2012 01:45:42 -0800 (PST) From: aaron morton Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: multipart/alternative; boundary="Apple-Mail=_7DEA6D9A-26ED-48DD-B84D-DB0BEFC740A4" Subject: Re: Tips for using OrderedPartitioner Date: Fri, 10 Feb 2012 22:45:39 +1300 In-Reply-To: To: user@cassandra.apache.org References: <2608CD6D-332E-47E5-B625-C8FB41EAC1ED@thelastpickle.com> Message-Id: X-Mailer: Apple Mail (2.1251.1) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_7DEA6D9A-26ED-48DD-B84D-DB0BEFC740A4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 > Also, if there's hot spot is there any way out of it, other than = restarting from scratch=85 A cluster with a changed partitioner is like a mule with a spinning = wheel. No one knows how it changed and danged if it knows how to return = your data .=20 (You cannot change it.) By uniform I meat evenly distributed across the range of values. That is = what the RandomPartitioner does by using the MD5 transform (also means = we know that the tokens have finite range). Cheers ----------------- Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 10/02/2012, at 8:31 AM, Tharindu Mathew wrote: > That sounds like writing a DB... indexing the index row.... :) >=20 > By making the keys uniform.... Do you mean like keep the initial X = characters the same or the last Y the same... Could you elaborate, = please? >=20 > Also, if there's hot spot is there any way out of it, other than = restarting from scratch... >=20 > On Tue, Jan 24, 2012 at 3:50 PM, R. Verlangen wrote: > If you would like to index your rows in an "index-row", you could also = choose for indexing the "index-rows". This will scale up for any needs = and create a tree structure. >=20 >=20 > 2012/1/24 aaron morton > Nothing I can thin of other than making the keys uniform. >=20 > Having a single index row with the RP can be a pain. Is there a way to = partition it ? >=20 > Cheers >=20 >=20 > ----------------- > Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com >=20 > On 23/01/2012, at 11:42 PM, Tharindu Mathew wrote: >=20 >> Hi, >>=20 >> We use Cassandra in a way we always want to range slice queries. = Because, of the tendency to create hotspots with OrderedPartioner we = decided to use RandomPartitioner. Then we would use, a row as an index = row, holding values of the other row keys of the CF. >>=20 >> I feel this has become a burden and would like to move to an = OrderedPartioner to avoid this work around. The index row workaround = which has become cumbersome when we query the data store. >>=20 >> Is there any tips we can follow to allow for lesser amount of hot = spots? >>=20 >> --=20 >> Regards, >>=20 >> Tharindu >>=20 >> blog: http://mackiemathew.com/ >>=20 >=20 >=20 >=20 >=20 >=20 > --=20 > Regards, >=20 > Tharindu >=20 > blog: http://mackiemathew.com/ >=20 --Apple-Mail=_7DEA6D9A-26ED-48DD-B84D-DB0BEFC740A4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Also, if there's hot spot is there any way = out of it, other than restarting from scratch=85
A = cluster with a changed partitioner is like a mule with a spinning wheel. = No one knows how it changed and danged if it knows how to return your = data . 
(You cannot change it.)

By = uniform I meat evenly distributed across the range of values. That is = what the RandomPartitioner does by using the MD5 transform (also means = we know that the tokens have finite = range).

Cheers


http://www.thelastpickle.com

On 10/02/2012, at 8:31 AM, Tharindu Mathew wrote:

That = sounds like writing a DB... indexing the index row.... :)

By = making the keys uniform.... Do you mean like keep the initial X = characters the same or the last Y the same... Could you elaborate, = please?

Also, if there's hot spot is there any way out of it, = other than restarting from scratch...

On Tue, Jan 24, 2012 at 3:50 PM, R. = Verlangen <robin@us2.nl> = wrote:
If you would like to index your rows in an "index-row", you could also = choose for indexing the "index-rows". This will scale up for any needs = and create a tree structure.


2012/1/24 aaron morton <aaron@thelastpickle.com>
Nothing I can thin of other = than making the keys uniform.

Having a single = index row with the RP can be a pain. Is there a way to partition it = ?

Cheers


-----------------
Aaron = Morton
Freelance Developer
@aaronmorton

On 23/01/2012, at 11:42 PM, Tharindu Mathew = wrote:

Hi,

We use = Cassandra in a way we always want to range slice queries. Because, of = the tendency to create hotspots with OrderedPartioner we decided to use = RandomPartitioner. Then we would use, a row as an index row, holding = values of the other row keys of the CF.

I feel this has become a burden and would like to = move to an OrderedPartioner to avoid this work around. The index row = workaround which has become cumbersome when we query the data = store.

Is there any tips we can follow to allow for lesser amount of = hot spots?

-- =
Regards,

Tharindu







-- =
Regards,

Tharindu



= --Apple-Mail=_7DEA6D9A-26ED-48DD-B84D-DB0BEFC740A4--