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

Stu Hood updated CASSANDRA-1035:
--------------------------------

    Description: 
To support multiple applications on top of a single Cassandra cluster (and to 
protect against badly behaving clients) having a very simple scheduler for 
client operations would be very beneficial.

Since all tasks are short lived, a sufficient scheduler would probably only 
need to manage the queue of incoming requests, and weight them based on an 
assigned ID. The ID could be dynamically determined by using ip, userid or 
keyspace for instance, and then each Runnable would be assigned an ID.

  was:
To support multiple applications on top of a single Cassandra cluster (and to 
protect against badly behaving clients) having a very simple scheduler for 
MUTATION-STAGE and READ-STAGE would be very beneficial.

Since all tasks are short lived, a sufficient scheduler would probably only 
need to manage the queue of incoming requests, and weight them based on an 
assigned ID. The ID could be dynamically determined by using ip, userid or 
keyspace for instance, and then each Runnable would be assigned an ID.


> Implement User/Keyspace throughput Scheduler
> --------------------------------------------
>
>                 Key: CASSANDRA-1035
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1035
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Stu Hood
>
> To support multiple applications on top of a single Cassandra cluster (and to 
> protect against badly behaving clients) having a very simple scheduler for 
> client operations would be very beneficial.
> Since all tasks are short lived, a sufficient scheduler would probably only 
> need to manage the queue of incoming requests, and weight them based on an 
> assigned ID. The ID could be dynamically determined by using ip, userid or 
> keyspace for instance, and then each Runnable would be assigned an ID.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to