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 6B4DFCBA3 for ; Fri, 7 Mar 2014 15:41:47 +0000 (UTC) Received: (qmail 79827 invoked by uid 500); 7 Mar 2014 15:41:44 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 79297 invoked by uid 500); 7 Mar 2014 15:41:43 -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 78417 invoked by uid 99); 7 Mar 2014 15:41:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Mar 2014 15:41:42 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 209.85.160.52 is neither permitted nor denied by domain of daniel.curry@arrayent.com) Received: from [209.85.160.52] (HELO mail-pb0-f52.google.com) (209.85.160.52) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Mar 2014 15:41:36 +0000 Received: by mail-pb0-f52.google.com with SMTP id rr13so4324178pbb.11 for ; Fri, 07 Mar 2014 07:41:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=b/csqJugx5zyHXYPOSyHKIRF8pm2QzQVflIOfHPXuj4=; b=A4zdh/xgwKkAw/YkGV6QQoJ8E63BctWBH7BQbbjGI4mPao6hj8bhF10gP71xXFXbAY y6wBb4MCJmCkSPanyhihvfCmm05/mNlPFGaWs0KlOOo7fVNaDuLxqP2qdJCc5derRMTY qt2BOsKJV3qhDxRBivSymZMURejtAJjfYstIQXoFt1OywYd78feHxO4Ais5KHZxPFqwD pJsCw6AKb9ym/mzEVT4R5X6A1l2L1DRSsL+iUMCrLilm9DJMlHnL8WS5JOe+jj+ElRst c4eNxI7z6NVXB8owEh3hdgGljgz2DulIKZg4q4tS43IC39pAu4nvYe3W2pn/Rj0DcLnp q1PA== X-Gm-Message-State: ALoCoQka7VnlUtCF+NFIkSYDcjtE1DyFX5TDmJp8ABvdPKVBKplVHjc0cEAeUcB5wlsHP6c2+Vil X-Received: by 10.68.189.33 with SMTP id gf1mr22395444pbc.111.1394206874987; Fri, 07 Mar 2014 07:41:14 -0800 (PST) Received: from [172.18.222.70] ([205.179.122.30]) by mx.google.com with ESMTPSA id lh13sm9263868pab.4.2014.03.07.07.41.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Mar 2014 07:41:14 -0800 (PST) Message-ID: <5319E899.6040201@arrayent.com> Date: Fri, 07 Mar 2014 07:41:13 -0800 From: Daniel Curry User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: user@cassandra.apache.org Subject: Re: replication_factor: ? References: <5319E518.5070409@arrayent.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------070602090704060908040009" X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------070602090704060908040009 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thank you. Your answer makes sense, Is this documented any where On 03/07/2014 07:37 AM, John Pyeatt wrote: > You really don't want to set your RF to the same value as the number > of nodes in your cluster for a variety of reasons. The biggest one > being that if you have a node go down, your entire database is > essentially down because you will be unable to fulfil any requests > because the RF can never be met. > > The number of nodes in the cluster is essentially independent from > your replication factor. > > The more important relationship is between your RF value, latency, and > what consistency level you want to use for your reads and writes. > > If you are going to use QUORUM consistency level it makes a little > more sense to have your RF set to an odd number. > > So for example if you have a 12 node cluster with an RF=3 and you are > using QUORUM consistency that means that 2 nodes ((RF+1)/2) have to be > able to fulfil the request. > > > > On Fri, Mar 7, 2014 at 9:26 AM, Daniel Curry > > wrote: > > I would like to know on what is the rule of thumb for > "replication_factor:" number? > I think the answer is depends on how many nodes one has? IE: three > nodes will be the > number 3. What would happen it I put the number 2 for a three > node cluster? > We are using both 3.2.4 and 3.1.3 ( that will be upgraded to > 3.2.4). > > Thank you. > > -- > Daniel Curry > > Sr. Linux System Administrator, Network Operations > > PGP : AD5A 96DC 7556 A020 B8E7 0E4D 5D5E 9BA5 C83E 8C92 > > Arrayent, Inc. > 2317 Broadway Street, Suite 20 > Redwood City, CA 94063 > daniel@arrayent.com > 650-260-4520 > > > > > -- > John Pyeatt > Singlewire Software, LLC > www.singlewire.com > ------------------ > 608.661.1184 > john.pyeatt@singlewire.com -- Daniel Curry Sr. Linux System Administrator, Network Operations PGP : AD5A 96DC 7556 A020 B8E7 0E4D 5D5E 9BA5 C83E 8C92 Arrayent, Inc. 2317 Broadway Street, Suite 20 Redwood City, CA 94063 daniel@arrayent.com 650-260-4520 --------------070602090704060908040009 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Thank you.  Your answer makes sense, Is this documented any where

On 03/07/2014 07:37 AM, John Pyeatt wrote:
You really don't want to set your RF to the same value as the number of nodes in your cluster for a variety of reasons. The biggest one being that if you have a node go down, your entire database is essentially down because you will be unable to fulfil any requests because the RF can never be met.

The number of nodes in the cluster is essentially independent from your replication factor.

The more important relationship is between your RF value, latency, and what consistency level you want to use for your reads and writes.

If you are going to use QUORUM consistency level it makes a little more sense to have your RF set to an odd number.

So for example if you have a 12 node cluster with an RF=3 and you are using QUORUM consistency that means that 2 nodes ((RF+1)/2) have to be able to fulfil the request.



On Fri, Mar 7, 2014 at 9:26 AM, Daniel Curry <daniel.curry@arrayent.com> wrote:
  I would like to know on what is the rule of thumb for "replication_factor:" number?
I think the answer is depends on how many nodes one has? IE: three nodes will be the
number 3.  What would happen it I put the number 2 for a three node cluster?
   We are using both 3.2.4 and 3.1.3 ( that will be upgraded to 3.2.4).

Thank you.

--
Daniel Curry

Sr. Linux System Administrator, Network Operations

PGP : AD5A 96DC 7556 A020 B8E7 0E4D 5D5E 9BA5 C83E 8C92

Arrayent, Inc.
2317 Broadway Street, Suite 20
Redwood City, CA 94063
daniel@arrayent.com
650-260-4520




--
John Pyeatt
Singlewire Software, LLC
www.singlewire.com
------------------
608.661.1184
john.pyeatt@singlewire.com

-- 
Daniel Curry

Sr. Linux System Administrator, Network Operations

PGP : AD5A 96DC 7556 A020 B8E7 0E4D 5D5E 9BA5 C83E 8C92

Arrayent, Inc.
2317 Broadway Street, Suite 20
Redwood City, CA 94063
daniel@arrayent.com
650-260-4520
--------------070602090704060908040009--