You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2017/03/20 08:22:42 UTC

[jira] [Resolved] (CASSANDRA-13352) Cassandra does not respond back in 12000ms

     [ https://issues.apache.org/jira/browse/CASSANDRA-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylvain Lebresne resolved CASSANDRA-13352.
------------------------------------------
    Resolution: Invalid

There is nothing indicative of a bug here, so please use the user mailing list for such inquiries.

But to elaborate quickly, your query will have read the entirely of the table (the need to add {{ALLOW FILTERING}} is C* telling you that the performance of this query is likely to very very bad) so it's not particularly surprising that it can't even answer in 12 seconds.

> Cassandra does not respond back in 12000ms
> ------------------------------------------
>
>                 Key: CASSANDRA-13352
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13352
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core, CQL
>            Reporter: Chirag
>             Fix For: 3.10
>
>
> I have my system with a table design, 
> Create Table lamscope_dashboard.events (
> ToolId text,
> Date timestamp,
> End_Time timestamp,
> DeviceId text,
> Logtype text,
> EventId text,
> MaterialId text,
> CfgId text,
> MaterialType text,
> Status text,
> SlotNo text,
> LotId text,
> RecipeId text,
> StepNum int ,
> Fromdevice text,
> Fromslot text,
> ToDevice text,
> ToSlot int ,
> FlowRecipeId text,
> Flowinfo text,
> CarrierId text,
> JobId text,
> Data text,
> PRIMARY KEY( ToolId, Date, MaterialId, DeviceId, EventId))
> WITH CLUSTERING ORDER BY (Date ASC,MaterialId ASC, DeviceId ASC)
> AND COMPRESSION = { 'sstable_compression' : 'SnappyCompressor'} ;
> Query 
> select * from events where eventid='xxxxx' allow filtering;
> It is a single instance cluster.
> System is not responding back in 12000 ms. 
> Query goes timeout.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)