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 C028E7830 for ; Sat, 13 Aug 2011 07:39:17 +0000 (UTC) Received: (qmail 16081 invoked by uid 500); 13 Aug 2011 07:39:15 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 15751 invoked by uid 500); 13 Aug 2011 07:39:11 -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 15736 invoked by uid 99); 13 Aug 2011 07:39:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Aug 2011 07:39:10 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yulinyen@gmail.com designates 209.85.215.44 as permitted sender) Received: from [209.85.215.44] (HELO mail-ew0-f44.google.com) (209.85.215.44) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Aug 2011 07:39:03 +0000 Received: by ewy19 with SMTP id 19so1525377ewy.31 for ; Sat, 13 Aug 2011 00:38:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=pWY1Vugt8xzhFtKlyhYGyCz9pj3uiRbEGm/uFKDNrro=; b=xT6e6CSzvz3X6va+TB+DawjPcOfV6rz8tPLJpp15FVdlta7tkS8XVr/vPph8e0Vnzh eEF6Z96OATVhSt6szSNaageUnBgQakSlfhSmUy48YJQXJK8VdTIno4JIiG4Chhawr+jv uVUNkzDUDOENAd9JJ0AMNem2PcBJLWJilQIeA= MIME-Version: 1.0 Received: by 10.14.33.65 with SMTP id p41mr141594eea.9.1313221121971; Sat, 13 Aug 2011 00:38:41 -0700 (PDT) Received: by 10.14.45.8 with HTTP; Sat, 13 Aug 2011 00:38:41 -0700 (PDT) Date: Sat, 13 Aug 2011 15:38:41 +0800 Message-ID: Subject: inconsistent counter value? From: Boris Yen To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=bcaec51ba0c57c953204aa5e1e12 --bcaec51ba0c57c953204aa5e1e12 Content-Type: text/plain; charset=ISO-8859-1 I posted a comment for Cassandra-3006 after 0.8.4 is released, but it seems not be noticed there, so I re-post here, wondering if anyone could help. ------------------------------- Follow the same steps posted on Cassandra-3006, after step 11, I check the counter on .152, the counter values changes from 1001 to 200. And then I follow the steps 12 and 13. The counter value of .151 is still 1001, but the counter value of .152 is still 200. After changing the consistencylevel to quorum and do the read again, this time the counter value of .152 became 1001. I am kind of confused, because at step 10, I can get 1001 on both nodes, how come the value of .152 changes to 200 when .151 is down. Is this the right behavior of current design? Regards Boris --bcaec51ba0c57c953204aa5e1e12 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I posted a comment for=A0Cassandra-3006 after 0.8.4 is rel= eased, but it seems not be noticed there, so I re-post here, wondering if a= nyone could help.
-------------------------------
Follow the same steps post= ed on Cassandra-3006, after step 11, I check the counter on .152, the count= er values changes from 1001 to 200. And then I follow the steps 12 and 13. = The counter value of .151 is still 1001, but the counter value of .152 is s= till 200. After =A0changing the consistencylevel to quorum and do the read = again, this time the counter value of .152 became 1001.
I am kind of confused, because at step 10, I can get 1001 on both nodes, ho= w come the value of .152 changes to 200 when .151 is down. Is this the righ= t behavior of current design?

Regards
Boris
--bcaec51ba0c57c953204aa5e1e12--