Details
-
New Feature
-
Status: Resolved
-
Low
-
Resolution: Later
-
None
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- relates to
-
CASSANDRA-1825 Separation of Data (Cached/Non-Cached)
- Resolved