I do not have a better knowledge about the Cassandra. As per my knowledge,
there is no such a tool. I believe, such a tool would be worth.
Thanks,
Indika
On Thu, Jan 20, 2011 at 6:15 PM, Mimi Aluminium wrote:
> Hi,
>
> I have a question that somewhat related to the above.
> Is there a tool that
Hi,
I have a question that somewhat related to the above.
Is there a tool that predicts the resource consumption (i.e, memory, disk,
CPU) in an offline mode? Means it is given with the storage conf
parameters, ks, CFs and data model, and then application parameters such
read/write average rates.
I have added my comments to this issue:
https://issues.apache.org/jira/browse/CASSANDRA-2006
Good luck!
On Thu, Jan 20, 2011 at 1:53 PM, indika kumara wrote:
> Thanks David We decided to do it at our client-side as the initial
> implementation. I will investigate the approaches for supporti
Thanks David We decided to do it at our client-side as the initial
implementation. I will investigate the approaches for supporting the fine
grained control of the resources consumed by a sever, tenant, and CF.
Thanks,
Indika
On Thu, Jan 20, 2011 at 3:20 PM, David Boxenhorn wrote:
> As far
As far as I can tell, if Cassandra supports three levels of configuration
(server, keyspace, column family) we can support multi-tenancy. It is
trivial to give each tenant their own keyspace (e.g. just use the tenant's
id as the keyspace name) and let them go wild. (Any out-of-bounds behavior
on th
+1 Are there JIRAs for these requirements? I would like to contribute from
my capacity.
As per my understanding, to support some muti-tenant models, it is needed to
qualified keyspaces' names, Cfs' names, etc. with the tenant namespace (or
id). The easiest way to do this would be to modify corre
Yes, the way I see it - and it becomes even more necessary for a
multi-tenant configuration - there should be completely separate
configurations for applications and for servers.
- Application configuration is based on data and usage characteristics of
your application.
- Server configuration is b
As the actual problem is mostly related to the number of CFs in the system
(may be number of the columns), I still believe that supporting exposing the
Cassandra ‘as-is’ to a tenant is doable and suitable though need some
fixes. That multi-tenancy model allows a tenant to use the programming
model
+1
On Wed, Jan 19, 2011 at 10:35 AM, Stu Hood wrote:
> Opened https://issues.apache.org/jira/browse/CASSANDRA-2006 with the
> solution we had suggested on the MultiTenant wiki page.
>
>
> On Tue, Jan 18, 2011 at 11:56 PM, David Boxenhorn wrote:
>
>> I think tuning of Cassandra is overly comple
I'm not sure that "you'd still want to retain the ability to individually
control how flushing happens on a per-cf basis in order to cater to
different workloads that benefit from different flushing behavior". It seems
to me like a good system-wide algorithm that works dynamically, and takes
into a
> Right now there is a one-to-one mapping between memtables and SSTables.
> Instead of that, would it be possible to have one giant memtable for each
> Cassandra instance, with partial flushing to SSTs?
I think a complication here is that, although I agree things need to
be easier to tweak at leas
Opened https://issues.apache.org/jira/browse/CASSANDRA-2006 with the
solution we had suggested on the MultiTenant wiki page.
On Tue, Jan 18, 2011 at 11:56 PM, David Boxenhorn wrote:
> I think tuning of Cassandra is overly complex, and even with a single
> tenant you can run into problems with to
I think tuning of Cassandra is overly complex, and even with a single tenant
you can run into problems with too many CFs.
Right now there is a one-to-one mapping between memtables and SSTables.
Instead of that, would it be possible to have one giant memtable for each
Cassandra instance, with parti
I've used an S3 style data model with a REST interface (varnish > nginx > tornado > cassandra), users do not see anything remotely cassandra like. AaronOn 19 Jan, 2011,at 10:27 AM, Stephen Connolly wrote:I would imagine it to be somewhat easy to implement this via a thrift wrapper so that each ten
I would imagine it to be somewhat easy to implement this via a thrift
wrapper so that each tenant is connecting to the proxy thrift server that
masks the fact that there are multiple tenants... or is that how people are
thinking about this
- Stephen
---
Sent from my Android phone, so random spell
As everyone says, it's not issues with the Keyspace directly as they are just a
container. It's the CF's in the keyspace, but let's just say keyspace cause
it's easier.
As things stand, if you allow point and click creation for keyspaces you will
hand over control of the memory requirements to
Hi Jeremy, thanks, I was really coming at it from the question of whether
keyspaces were a functional basis for multitenancy in Cassandra. I think
the MT issues discussed on the wiki page are the , but I'd like to get a
better understanding of the core issue of keyspaces and then try to get that
o
Feel free to use that wiki page or another wiki page to collaborate on more
pressing multi tenant issues. The wiki is editable by all. The MultiTenant
page was meant as a launching point for tracking progress on things we could
think of wrt MT.
Obviously the memtable problem is the largest co
Hi Indika, I've done a lot of work using the keyspace per tenant model, and
I'm seeing big problems with the memory consumption, even though it's
certainly the most clean way to implement it. Luckily, before I used the
keyspace per tenant approach, I'd implemented my system using a single
keyspace
Hi Aaron,
I read some articles about the Cassandra, and now understand a little bit
about trade-offs.
I feel the goal should be to optimize memory as well as performance. I have
to consider the number of column families, the columns per a family, the
number of rows, the memtable’s threshold, and
Hi Aaron,
I appreciate your help. I am a newbie to Cassandra - just began to study the
code-base.
Do you suggest the following approach?
*1) No changes are in either keyspace names or column family names but the
row-key would be ‘the actual row key’ + 'tenant ID'. It is needed to keep
separate m
Moving to user list
On Tue, Jan 18, 2011 at 4:05 PM, Aaron Morton wrote:
> Have a read about JVM heap sizing here
> http://wiki.apache.org/cassandra/MemtableThresholds
>
> If you let people create keyspaces with a mouse click you will soon run out
> of memory.
>
> I use Cassandra to provide a sel
22 matches
Mail list logo
