cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nirmal Ranganathan (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-1035) Implement User/Keyspace throughput Scheduler
Date Tue, 29 Jun 2010 17:47:50 GMT


Nirmal Ranganathan updated CASSANDRA-1035:

    Attachment: 0001-Adding-the-RequestScheduler-abstraction-and-a-simple.patch

Renamed FairShare to RoundRobin and added the NonBlockingHashmap.

0001 - Scheduler addition + configuration changes
0002 - Thrift changes
0003 - Avro Changes
0004 - Test case for RoundRobinScheduler

> Implement User/Keyspace throughput Scheduler
> --------------------------------------------
>                 Key: CASSANDRA-1035
>                 URL:
>             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,
> 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.

View raw message