[
https://issues.apache.org/jira/browse/CASSANDRA-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073653#comment-13073653
]
Ryan King commented on CASSANDRA-1379:
--------------------------------------
We have use cases along these lines too. We've had to resort to bumping the
read threads up much higher (128 or 256) for highly cached workloads.
> 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
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
