Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 29 Mar 2011 07:17:05 +0000 (UTC)
From: "Tey Kar Shiang (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1008219186.18368.1301383025784.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (CASSANDRA-2401) getColumnFamily() return null,
 which is not checked in ColumnFamilyStore.java scan() method, causing
 Timeout Exception in query
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

getColumnFamily() return null, which is not checked in ColumnFamilyStore.java scan() method, causing Timeout Exception in query
-------------------------------------------------------------------------------------------------------------------------------

                 Key: CASSANDRA-2401
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2401
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 0.7.4
         Environment: Hector 0.7.0-28, Cassandra 0.7.4, Windows 7, Eclipse
            Reporter: Tey Kar Shiang


ColumnFamilyStore.java, line near 1680, "ColumnFamily data = getColumnFamily(new QueryFilter(dk, path, firstFilter))", the data is returned null, causing NULL exception in "satisfies(data, clause, primary)" which is not captured. The callback got timeout and return a Timeout exception to Hector.

The data is empty, as I traced, I have the the columns Count as 0 in removeDeletedCF(), which return the null there. (I am new and trying to understand the logics around still). Instead of crash to NULL, could we bypass the data?

About my test:
A stress-test program to add, modify and delete data to keyspace. I have 30 threads simulate concurrent users to perform the actions above, and do a query to all rows periodically. I have Column Family with rows (as File) and columns as index (e.g. userID, fileType).

No issue on the first day of test, and stopped for 3 days. I restart the test on 4th day, 1 of the users failed to query the files (timeout exception received). Most of the users are still okay with the query.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira