You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Burroughs (JIRA)" <ji...@apache.org> on 2011/01/25 15:56:46 UTC

[jira] Commented: (CASSANDRA-1379) Uncached row reads may block cached reads

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

Chris Burroughs commented on CASSANDRA-1379:
--------------------------------------------

Is there any existing mechanism to detect and measure if this is occurring?

> Uncached row reads may block cached reads
> -----------------------------------------
>
>                 Key: CASSANDRA-1379
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1379
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: David King
>            Assignee: Javier Canillas
>            Priority: Minor
>             Fix For: 0.7.2
>
>         Attachments: CASSANDRA-1379.patch
>
>
> The cap on the number of concurrent reads appears to cap the *total* number of concurrent reads instead of just capping the reads that are bound for disk. That is, given N concurrent readers if all of them are busy waiting on disk, even reads that can be served from the row cache will block waiting for them.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.