[
https://issues.apache.org/jira/browse/CASSANDRA-8059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mck resolved CASSANDRA-8059.
----------------------------
Resolution: Won't Fix
See the discussion in CASSANDRA-8032
> CQL requests need to go through the request scheduler
> -----------------------------------------------------
>
> Key: CASSANDRA-8059
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8059
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: mck
>
> Implementing CASSANDRA-8032 it seems that no cql/cql3 requests go through the
> request scheduler. I'm guessing they never have?
> If this is to be fixed/implemented then it looks like that there's a number
> of methods in `CassandraServer` that need to call `schedule(timeout)`.
> The alternative is to remove the request scheduler along with thrift?
> Regarding that choice see my opinion from CASSANDRA-8032…
> {quote}
> … … The request scheduler is a useful concept but i think that setups with
> enough nodes often favour separate clusters rather than either creating
> separate virtual datacenters or using the request scheduler. To give the
> request scheduler another, and more flexible, implementation could especially
> help those users that don't yet have enough nodes to warrant separate
> clusters, or even separate virtual datacenters. On such smaller clusters
> cassandra can still be seen as an unstable technology because poor
> consumers/schemas can easily affect, even bring down, a whole cluster. … …
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
