[ https://issues.apache.org/jira/browse/CASSANDRA-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nirmal Ranganathan updated CASSANDRA-1035: ------------------------------------------ Attachment: 1035-v3.patch Ah ok, that works. Thanks that's made it much cleaner. I've removed the wait/notify and used a SynchronousQueue. I've also moved the initialization to DD and removed initialize(). > Implement User/Keyspace throughput Scheduler > -------------------------------------------- > > Key: CASSANDRA-1035 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1035 > Project: Cassandra > Issue Type: Improvement > Affects Versions: 0.7 > 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-Add-options-for-throttling.patch, 1035-v2.txt, 1035-v3.patch, > Cassandra-1035.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.