cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CASSANDRA-1035) Implement User/Keyspace throughput Scheduler
Date Tue, 29 Jun 2010 21:34:50 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883704#action_12883704
] 

Stu Hood edited comment on CASSANDRA-1035 at 6/29/10 5:34 PM:
--------------------------------------------------------------

Adding 0005 which fixes two small problems: Nirmal, can you double check the fixes?

EDIT: Shoot... apparently I was so busy bikeshedding that I missed the big problem: the schedule()
method doesn't limit the number of threads that it lets run simultaneously per id, so it won't
actually perform any throttling. This will probably require a bit of refactoring. Sorry!

      was (Author: stuhood):
    Adding 0005 which fixes two small problems: Nirmal, can you double check the fixes? Otherwise,
this has a +1 from me.
  
> 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
>            Assignee: Nirmal Ranganathan
>             Fix For: 0.7
>
>         Attachments: 0001-Adding-the-RequestScheduler-abstraction-and-a-simple.patch,
0002-Thrift-related-changes-for-RequestScheduler-added-a-.patch, 0003-Avro-related-changes-for-RequestScheduler.patch,
0004-Test-case-for-RoundRobinScheduler.patch, 0005-Minimize-queue-creation-and-remove-redundant-schedul.patch
>
>
> 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.


Mime
View raw message