From user-return-9018-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Sun Sep 05 15:48:29 2010
Return-Path: <user-return-9018-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: (qmail 78456 invoked from network); 5 Sep 2010 15:48:29 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 5 Sep 2010 15:48:29 -0000
Received: (qmail 18611 invoked by uid 500); 5 Sep 2010 15:48:27 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 18563 invoked by uid 500); 5 Sep 2010 15:48:26 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 18554 invoked by uid 99); 5 Sep 2010 15:48:26 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Sep 2010 15:48:26 +0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of edlinuxguru@gmail.com designates 209.85.214.44 as permitted sender)
Received: from [209.85.214.44] (HELO mail-bw0-f44.google.com) (209.85.214.44)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Sep 2010 15:48:17 +0000
Received: by bwz9 with SMTP id 9so3485490bwz.31
        for <user@cassandra.apache.org>; Sun, 05 Sep 2010 08:47:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:received:date:message-id
         :subject:from:to:content-type;
        bh=bf0IP0uVRq1SyvkOXQFAVsmJtSqUCRjzgJh7agtpSwI=;
        b=QrhOPiNt/1uCQeeGMuc0H38G1njXc4D+LLo4BUMPbeUmzHPLInnP5e35rsy2kgzo8u
         vN05hN6Et7flZo002H6bDj0Ij07CVQvYYv2GH3ikcfhWfOthrWy5Bwab8U7mMQzJ6eFL
         ETkIJIJmMWwiSSy392yVBsmBiC2RI3UHw9nkI=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=rUkl2BLYF8bkdmwjAW8f4mn40hFIM0VUIlFl3iSxFitn8h3bKiuXHr0rIzjxFAD3D+
         aWG+x4Txj2LXUl9dUnxUoTSWLJQ24GW5jk1oEFjlDbaWougYo4uflblXSdXzDOXqAq4X
         sTdYbyjPMGbQc/NrqCv081h/LUT5ufPy3RkYY=
MIME-Version: 1.0
Received: by 10.204.65.145 with SMTP id j17mr2023822bki.209.1283701677049;
 Sun, 05 Sep 2010 08:47:57 -0700 (PDT)
Received: by 10.204.118.1 with HTTP; Sun, 5 Sep 2010 08:47:57 -0700 (PDT)
Date: Sun, 5 Sep 2010 11:47:57 -0400
Message-ID: <AANLkTikVAAsXkRLwdYrKqQi3KL0LaCP62k2qNxO4QHB5@mail.gmail.com>
Subject: anyone want to talk about read_repair_chance
From: Edward Capriolo <edlinuxguru@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

Read repair chance looks to be an awesome feature. We have a pretty
high cache hit rate so I would assume read repair chance would reduce
a lot of bandwidth and disk activity across our cluster. Does anyone
have some statistics or experiences they want to share?

Edward