cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8032) User based request scheduler
Date Sun, 05 Oct 2014 21:45:34 GMT


Aleksey Yeschenko commented on CASSANDRA-8032:

As for multitenancy support - you aren't alone here, the request for it comes up relatively
often. But I believe that it's something that should be designed from top to bottom, and it's
going to be a major change encapsulating a lot of layers, and not from bottom up, via half

I think we'll have it, eventually, but likely not in the 3.x line - there is some technical
debt to be paid off first, and some more pressing features. That said, again, I do agree with
you that it would be nice to have, definitely, so no need to sell me on it - we are on the
same side here. It's just that the time for it hasn't come, yet.

> User based request scheduler
> ----------------------------
>                 Key: CASSANDRA-8032
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: mck
>            Assignee: mck
>            Priority: Minor
>              Labels: patch
>         Attachments: v1-0001-CASSANDRA-8032-User-based-request-scheduler.txt
> Today only a keyspace based request scheduler exists.
> Post CASSANDRA-4898 it could be possible to implement a request_scheduler based on users
(from system_auth.credentials) rather than keyspaces. This could offer a finer granularity
of control, from read-only vs read-write users on keyspaces, to application dedicated vs ad-hoc
users. Alternatively it could also offer a granularity larger and easier to work with than
per keyspace.
> The request scheduler is a useful concept but i think that setups with enough nodes often
favour separate clusters rather than either creating separate virtual datacenters or using
the request scheduler. To give the request scheduler another, and more flexible, implementation
could especially help those users that don't yet have enough nodes to warrant separate clusters,
or even separate virtual datacenters. On such smaller clusters cassandra can still be seen
as an unstable technology because poor consumers/schemas can easily affect, even bring down,
a whole cluster.
> I haven't look into the feasibility of this within the code, but it comes to mind as
rather simple, and i would be interested in offering a patch if the idea carries validity.

This message was sent by Atlassian JIRA

View raw message