[ https://issues.apache.org/jira/browse/CASSANDRA-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hanna updated CASSANDRA-1035: ------------------------------------ Fix Version/s: 0.7 For multi-tenant clusters, this will be very important so we're hoping that we can help get this done prior to the 0.7 release. > 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 > Fix For: 0.7 > > > 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.