cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3687) Local range scans are not run on the read stage
Date Mon, 02 Jan 2012 14:54:31 GMT

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

Jonathan Ellis commented on CASSANDRA-3687:
-------------------------------------------

Look at SP.LocalReadRunnable for how to do this safely. Simplest fix would be to just continue
routing all range scans over MessagingService.
                
> Local range scans are not run on the read stage
> -----------------------------------------------
>
>                 Key: CASSANDRA-3687
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3687
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Priority: Minor
>             Fix For: 1.2
>
>
> Running directly on the client request/StorageProxy thread means we're now allowing one
range scan per thrift thread instead of one per read stage thread [which may be more, or less,
depending on thrift server mode], and it bypasses the "drop hopeless requests" overcapacity
protection built in there. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message