cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10467) QoS for Queries
Date Thu, 08 Oct 2015 04:13:26 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-10467:
---------------------------------------
    Fix Version/s: 3.x

> QoS for Queries
> ---------------
>
>                 Key: CASSANDRA-10467
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10467
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benjamin Coverston
>             Fix For: 3.x
>
>
> Background: As an OLTP system that is based on pipelined execution worker pools can be
saturated with long(er) running calls. When the system is under stress, those long running
calls can make requests that should be short lived requests take a much longer period of time.
> Introduce the concept of QoS into Cassandra for client queries. A few ideas:
> 1. Allow clients to specify a QoS to be sent to Cassandra from the driver as part of
the protocol.
> 2. Allow different requests to be tagged based on some simple criteria (perhaps configured)
(i.e. ALLOW FILTERING was part of the query)
> 3. QOS based on the LUN that is accessed (SSDs get higher QOS than the RAID5)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message