Hi, CASSANDRA-8303 talks about more granular control at the query level. What we are looking at is throttling on the basis of the number of queries received for different keyspaces. This is what request_scheduler and request_scheduler_options provide for clients connecting via thrift.
Regards On Wed, Nov 28, 2018 at 2:27 PM dinesh.jo...@yahoo.com.INVALID <dinesh.jo...@yahoo.com.invalid> wrote: > I think what you're looking for might be solved by CASSANDRA-8303. > However, I am not sure if anybody is working on it. Generally you want to > create different clusters for users to physically isolate them. What you > propose has been discussed in the past and it is something that is > currently unsupported. > > Dinesh > > > On Tuesday, November 27, 2018, 11:05:32 PM PST, Shaurya Gupta < > shaurya.n...@gmail.com> wrote: > > > Hi, > > We want to throttle maximum queries on any keyspace for clients connecting > via CQL native transport. This option is available for clients connecting > via thrift by property of request_scheduler in cassandra.yaml. > Is there some option available for clients connecting via CQL native > transport. > If not is there any plan to do so in future. > It is a must have feature if we want to support multiple teams on a single > cassandra cluster or to prevent one keyspace from interfering with the > performance of the other keyspaces. > > Regards > Shaurya Gupta > > > -- Shaurya Gupta
