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 065D83C97 for ; Mon, 2 May 2011 19:30:59 +0000 (UTC) Received: (qmail 65152 invoked by uid 500); 2 May 2011 19:30:57 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 65126 invoked by uid 500); 2 May 2011 19:30:57 -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 65118 invoked by uid 99); 2 May 2011 19:30:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 May 2011 19:30:57 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=FREEMAIL_FROM,FS_REPLICA,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of etamme@gmail.com designates 209.85.161.44 as permitted sender) Received: from [209.85.161.44] (HELO mail-fx0-f44.google.com) (209.85.161.44) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 May 2011 19:30:50 +0000 Received: by fxm15 with SMTP id 15so4484124fxm.31 for ; Mon, 02 May 2011 12:30:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=Xs00JI5d3DNgLye8nUlYcDUwvHzpBxVwYTxXmRLoDQA=; b=C4eX18Tp3kybb2IVYVcCVtb0knRNZfYQjmQJz9A9QDoj2IXfEyeSwFe4yDkwZCyjq8 GmDWeymCnfPMTK7s7oWEjc5vW1UDWDZC2Jb82XkA7N8nuEU0fenabn59E36kvW9vvmGk LKr5mIqaw0836qQoklqI1ZbbYl4H80Log+0M4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=tLP8ZViosGDCfbSlu3XkoinTsmIq0axHug+lMti1vq4W8vkOJU/HstzsVAH/QyLSc7 etOLPNFVqJdoOXjDoiFrhX3ocjmsqArJrTqNkusBNh7dTMz65jnrrtnjwn7USEyzoBG7 I9yIaj72lvTWcX6Ozs+rgiDZimJHr71xDzNtI= MIME-Version: 1.0 Received: by 10.223.95.198 with SMTP id e6mr523119fan.13.1304364630492; Mon, 02 May 2011 12:30:30 -0700 (PDT) Received: by 10.223.73.203 with HTTP; Mon, 2 May 2011 12:30:30 -0700 (PDT) In-Reply-To: References: <707E9B09-AA4A-4C2A-A43B-114CC38DC9FF@thelastpickle.com> Date: Mon, 2 May 2011 15:30:30 -0400 Message-ID: Subject: Re: Replica data distributing between racks From: Eric tamme To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Mon, May 2, 2011 at 3:22 PM, Jonathan Ellis wrote: > On Mon, May 2, 2011 at 2:18 PM, aaron morton wr= ote: >> When the NTS selects replicas in a DC it orders the tokens available in = =A0the DC, then (in the first pass) iterates through them placing a replica= in each unique rack. =A0e.g. if the RF in each DC was 2, the replicas woul= d be put on 2 unique racks if possible. So the lowest token in the DC will = *always* get a write. > > It's supposed to start w/ the node closest to the token in each DC, so > that shouldn't be the case unless you are using BOP/OPP instead of RP. > I am using a RandomPartitioner as shown below: Cluster Information: Snitch: org.apache.cassandra.locator.PropertyFileSnitch Partitioner: org.apache.cassandra.dht.RandomPartitioner So as far as "closeness" .. how does that get factored in when using a PropertyFileSnitch? Is one rack closer than the other? In reality for each data center there are two nodes in the same rack on the same switch, but I set the topology file up to have 2 racks per data center specifically so I would get distribution. -Eric