You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/08/11 22:11:32 UTC

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

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

Jonathan Ellis updated CASSANDRA-1379:
--------------------------------------

           Issue Type: New Feature  (was: Bug)
        Fix Version/s: 0.7.1
    Affects Version/s:     (was: 0.6.4)
             Priority: Minor  (was: Major)

Are you suggesting splitting the read stage into check-cache and fetch-data stages?

> 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
>            Priority: Minor
>             Fix For: 0.7.1
>
>
> 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.