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 9390571D0 for ; Wed, 12 Oct 2011 23:27:02 +0000 (UTC) Received: (qmail 84274 invoked by uid 500); 12 Oct 2011 23:27:00 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 84249 invoked by uid 500); 12 Oct 2011 23:27:00 -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 84241 invoked by uid 99); 12 Oct 2011 23:27:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Oct 2011 23:27:00 +0000 X-ASF-Spam-Status: No, hits=-1.4 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gcdcu-cassandra-user-1@m.gmane.org designates 80.91.229.12 as permitted sender) Received: from [80.91.229.12] (HELO lo.gmane.org) (80.91.229.12) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Oct 2011 23:26:51 +0000 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RE8Bx-0001F0-CR for user@cassandra.apache.org; Thu, 13 Oct 2011 01:26:29 +0200 Received: from 192.71.175.2 ([192.71.175.2]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 13 Oct 2011 01:26:29 +0200 Received: from gopalakrishnan.r87 by 192.71.175.2 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 13 Oct 2011 01:26:29 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: user@cassandra.apache.org From: Gopalakrishnan R Subject: Re: [RELEASE CANDIDATE] Apache Cassandra 1.0.0-rc2 released - Read data inconsistancy Date: Wed, 12 Oct 2011 23:26:18 +0000 (UTC) Lines: 37 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 192.71.175.2 (Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; SLCC1; .NET CLR 2.0.50727; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)) X-Virus-Checked: Checked by ClamAV on apache.org I am right now evaluating Cassandra 1.0.0-rc2 with a super column family with one super column and variable (from 7 to 18) number of sub columns inside that one super column. The column family has about 20 million rows (keys) and about 200,000 million sub columns (records) in total. I use a 3 node linux cluster with replication factor as three and read/write consistancy level as hector client default (QUORUM). The column family uses SnappyCompressor and has read repair disabled The issue I face is that when I query the super column for a particular key using hector-core-0.8.0-2, the data retrieved is inconsistent. I mean, for the key that I use to fetch data, there are 7 sub columns actually. But the query returns 1 or 3 sub columns depending on which nodes respond to it. (I tested by bringing down each one of the three nodes in turn). When I tried to fetch the data for the same key using cassandra-cli tool, I get all the 7 sub columns for both the consistancy levels ONE and QUORUM. So is this a inconsistancy issue or compatibility problem between Cassandra 1.0.0-rc2 and hector-core-0.8.0-2? I tested with same column family and same code in Cassandra 1.0.0-beta1 version and it works fine there. Because I am new to Cassandra and been working with it for only two months I paste the code I used to fetch the data below: superColumnQuery = HFactory.createSuperColumnQuery (keyspaceOperator, stringSerializer, stringSerializer, stringSerializer, stringSerializer); superColumnQuery.setColumnFamily(cfName).setKey (key).setSuperName(scName); result=superColumnQuery.execute(); superColumn=result.get(); columnList=superColumn.getColumns(); Please suggest me on the problem and the solution.