[ https://issues.apache.org/jira/browse/CASSANDRA-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897430#action_12897430 ]
David King commented on CASSANDRA-1379: --------------------------------------- Not being familiar with the implementation I'm not sure I'm suggesting anything, but that sounds sane. Or checking the cache first in the stage previous > 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.