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 00D85DF10 for ; Tue, 13 Nov 2012 02:12:36 +0000 (UTC) Received: (qmail 6049 invoked by uid 500); 13 Nov 2012 02:12:33 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 6019 invoked by uid 500); 13 Nov 2012 02:12:33 -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 6011 invoked by uid 99); 13 Nov 2012 02:12:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Nov 2012 02:12:33 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.212.44] (HELO mail-vb0-f44.google.com) (209.85.212.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Nov 2012 02:12:26 +0000 Received: by mail-vb0-f44.google.com with SMTP id fc26so7693609vbb.31 for ; Mon, 12 Nov 2012 18:12:05 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=YdCX3on3TnkxvAFBuejU1mVyB/UEaQ4Vw6d9fE3lJeg=; b=Lk9boAJ3Apuwoi6QxbrHz2dqlCZMkPajOokdM9xQ16QBKv+YRcygq0OP8sQYvy5Hg/ y1oDmYMu2ZKjM5tiqS3pWAIYAYPWA1MI2OSRb3Neg0IQb9Eq1XlLE+1X3LMnj5HFPBIG QdDyRN32BCwWXhPGz/Ow8FTsyQxsyY39s3ze9t5rvgzPVKn9B8Vjt6j0uv0vXK92zbbe BVd/cME9DU7YNsES2Ycyfm8YzRWipTQX3bJMNIPiYARz6IEpUa6D3w1PjTEys+fV44+9 fhSA8VEi+7H17rmKOKD+RqWGXtcfuxQHFS6+8iK6fz3cpyInkB+GijB+13hwAvRq6v1z lXrw== MIME-Version: 1.0 Received: by 10.220.154.68 with SMTP id n4mr3360280vcw.22.1352772725748; Mon, 12 Nov 2012 18:12:05 -0800 (PST) Received: by 10.58.210.132 with HTTP; Mon, 12 Nov 2012 18:12:05 -0800 (PST) In-Reply-To: References: Date: Mon, 12 Nov 2012 18:12:05 -0800 Message-ID: Subject: Re: Counter column families (pending replicate on write stage tasks) From: Rob Coli To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmjD4n3ui8VrThPjAgNOz1XjR0qivX2PUmPMtwA7XygVlC4L07jMkq3rzm8gDzJ9h+/0U67 X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Nov 12, 2012 at 3:35 PM, cem wrote: > We are currently facing a performance issue with counter column families. I > see lots of pending ReplicateOnWriteStage tasks in tpstats. Then I disabled > replicate_on_write. It helped a lot. I want to use like that but I am not > sure how to use it. Quoting Sylvain, one of the primary authors/maintainers of the Counters support... https://issues.apache.org/jira/browse/CASSANDRA-3868 " I don't disagree about the efficiency of the valve, but at what price? 'Bootstrapping a node will make you lose increments (you don't know which ones, you don't know how many and this even if nothing goes wrong)' is a pretty bad drawback. That is pretty much why that option makes me uncomfortable: it does give you better performance, so people may be tempted to use it. Now if it was only a matter of replicating writes only through read-repair/repair, then ok, it's pretty dangerous but it's rather easy to explain/understand the drawback (if you don't lose a disk, you don't lose increments, and you'd better use CL.ALL or have read_repair_chance to 1). But the fact that it doesn't work with bootstrap/move makes me wonder if having the option at all is not making a disservice to users. " IOW, don't be tempted to turn off replicate_on_write. It breaks counters. If you are under capacity at a steady state, increase capacity. =Rob -- =Robert Coli AIM>ALK - rcoli@palominodb.com YAHOO - rcoli.palominob SKYPE - rcoli_palominodb