Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <28066092.118431277833252450.JavaMail.jira@thor>
Date: Tue, 29 Jun 2010 13:40:52 -0400 (EDT)
From: "Nirmal Ranganathan (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Updated: (CASSANDRA-1035) Implement User/Keyspace throughput
 Scheduler
In-Reply-To: <17623898.8461272561235266.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Nirmal Ranganathan updated CASSANDRA-1035:
------------------------------------------

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

> 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: 0003-Thrift-related-changes-for-RequestScheduler-added-a-.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.