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 01EBCDFE3 for ; Mon, 19 Nov 2012 19:52:35 +0000 (UTC) Received: (qmail 90962 invoked by uid 500); 19 Nov 2012 19:52:32 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 90942 invoked by uid 500); 19 Nov 2012 19:52:32 -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 90934 invoked by uid 99); 19 Nov 2012 19:52:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Nov 2012 19:52:32 +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.223.172] (HELO mail-ie0-f172.google.com) (209.85.223.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Nov 2012 19:52:26 +0000 Received: by mail-ie0-f172.google.com with SMTP id 9so8147445iec.31 for ; Mon, 19 Nov 2012 11:52:04 -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=U/RCdNUaOEwLMtN3ShsgfxTPibdOQPzhOdYIFyy2Ltw=; b=UZNpuLI7iO0KAQWUgqmg5I2aBvtUiqoyF0My2nn1z4OpiCutf/rS8vBcJvCYg455H5 4QPS6OXCheQ/rTuwWiQYPT9hS1AafuyLoHdRml+kvB7HXPH3g6bMJ3GWDuGO7hYyWDGw 4GbBMarHpeoU1CjsZT/NicSY2EvTyT+8OcNRDS64M3w8uxNytfndpyLugpNhw2On0Syq VO/cG01PyUapm/LIrcHtWFH78x1FToMnGI7TYkXzpzXK2OrScZr4teTGDPqln0FIa6ua LaQ9gkNFFdDcsu/6hxBgapK7i4Ia1BbYJki8T/7HWZmC0ABFqQdvrkjUIq96duYnPJgu i0Tg== MIME-Version: 1.0 Received: by 10.50.159.229 with SMTP id xf5mr7830512igb.0.1353354724567; Mon, 19 Nov 2012 11:52:04 -0800 (PST) Received: by 10.50.96.161 with HTTP; Mon, 19 Nov 2012 11:52:04 -0800 (PST) In-Reply-To: References: Date: Mon, 19 Nov 2012 11:52:04 -0800 Message-ID: Subject: Re: Upgrade 1.1.2 -> 1.1.6 From: Rob Coli To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlrWLfVUm/C2sdC0n21QC419G8mDlJR4Yce26sJWB7D9ukEoLYONfFCNghLVZqhE410nFBQ X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Nov 15, 2012 at 6:21 AM, Alain RODRIGUEZ wrote: > We had an issue with counters over-counting even using the nodetool drain > command before upgrading... You're sure the over-count was caused by the upgrade?Counts can be counted on (heh) to overcount. What is the scale of the over-count? Also, do you realize that drain doesn't actually prevent over-replay, though it should? https://issues.apache.org/jira/browse/CASSANDRA-4446 Check for replayed operations in the system log.. " grep -i replay /path/to/system.log " (I see further down thread that your logs do in fact contain replay. Please comment to this effect, and how negative the experience is for counts, on 4446?) > I saw that the "sudo apt-get install cassandra" stop the server and restart > it automatically. So it updated without draining and restart before I had > the time to reconfigure the conf files. Is this "normal" ? Is there a way to > avoid it ? https://issues.apache.org/jira/browse/CASSANDRA-2356 Perhaps if you comment on here you can help convince the debian packager that auto-starting a distributed database when you install or upgrade its package has negative operational characteristics. > After both of these updates I saw my current counters increase without any > reason. > > Did I do anything wrong ? Expecting counters to not over-count may qualify as "wrong." But your process seems reasonable. =Rob -- =Robert Coli AIM>ALK - rcoli@palominodb.com YAHOO - rcoli.palominob SKYPE - rcoli_palominodb