Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 9 Jan 2014 06:11:51 +0000 (UTC)
From: "Pavel Yaskevich (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12681357.1385495751403.67004.1389247911209@arcas>
In-Reply-To: <JIRA.12681357.1385495751403@arcas>
References: <JIRA.12681357.1385495751403@arcas>
Subject: [jira] [Commented] (CASSANDRA-6407) CQL/Thrift request hangs
 forever when querying more than certain amount of data
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866359#comment-13866359 ] 

Pavel Yaskevich commented on CASSANDRA-6407:
--------------------------------------------

Yeah, they look similar but at lease we can reproduce, can you try one more thing please while you are on it - disable vnodes and try hsha with your data?

> CQL/Thrift request hangs forever when querying more than certain amount of data
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6407
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6407
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Oracle Linux 6.4, JDK 1.7.0_25-b15, Cassandra 2.0.2
>            Reporter: Nikolai Grigoriev
>         Attachments: cassandra.jstack.gz, cassandra.yaml, cassandra6407test.cql.gz, system.log.gz
>
>
> I have a table like this (slightly simplified for clarity):
> {code}
> CREATE TABLE my_test_table (
> 		uid  uuid,
> 		d_id	 uuid,
> 		a_id	 uuid,	
> 		c_id	text,
> 		i_id	blob,	
> 		data	text,
> 		PRIMARY KEY ((uid, d_id, a_id), c_id, i_id)
> );
> {code}
> I have created about over a hundred (117 to be specific) of sample entities with the same row key and different clustering keys. Each has a blob of approximately 4Kb.
> I have tried to fetch all of them with a query like this via CQLSH:
> {code}
> select * from my_test_table where uid=44338526-7aac-4640-bcde-0f4663c07572 and a_id=00000000-0000-4000-0000-000000000002 and d_id=00000000-0000-1e64-0000-000000000001 and c_id='list-2'
> {code}
> This query simply hangs in CQLSH, it does not return at all until I abort it.
> Then I started playing with LIMIT clause and found that this query returns instantly (with good data) when I use LIMIT 55 but hangs forever when I use LIMIT 56.
> Then I tried to just query all "i_id" values like this:
> {code}
> select i_id from my_test_table where uid=44338526-7aac-4640-bcde-0f4663c07572 and a_id=00000000-0000-4000-0000-000000000002 and d_id=00000000-0000-1e64-0000-000000000001 and c_id='list-2'
> {code}
> And this query returns instantly with the complete set of 117 values. So I started thinking that it must be something about the total size of the response, not the number of results or the number of columns to be fetches in slices. And I have tried another test:
> {code}
> select cdata from my_test_table where uid=44338526-7aac-4640-bcde-0f4663c07572 and a_id=00000000-0000-4000-0000-000000000002 and d_id=00000000-0000-1e64-0000-000000000001 and c_id='list-2' LIMIT 63
> {code}
> This query returns instantly but if I change the limit to 64 it hangs forever. Since my blob is about 4Kb for each entity it *seems* like the query hangs when the total size of the response exceeds 252..256Kb. Looks quite suspicious especially because 256Kb is such a particular number. I am wondering if this has something to do with the result paging.
> I did not test if the issue is reproducible outside of CQLSH but I do recall that I observed somewhat similar behavior when fetching relatively large data sets.
> I can consistently reproduce this problem on my cluster. I am also attaching the jstack output that I have captured when CQLSH was hanging on one of these queries.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)