Hi Thanks,
The schema is different. Putting a tenant id as first partition key will
make spark logic more complex ( filtering is needed in search-all).
> There's also the issue of lots of memtables flushing to disk during
commit log rotations. Can be problematic.
If this is the case, I think Ca
There's also the issue of lots of memtables flushing to disk during commit
log rotations. Can be problematic.
On Wed, Apr 6, 2016 at 2:08 PM Michael Penick
wrote:
> Are the tenants using the same schema? If so, you might consider using the
> tenant's ID as part of the primary key for the tables
Are the tenants using the same schema? If so, you might consider using the
tenant's ID as part of the primary key for the tables they have in common.
If they're all using different, largish schemas I'm not sure that Cassandra
is well suited to that type of multi-tenancy. There's the per overhead
m
So, best case, with 50 tables per tenant, you could support less than ten
tenants ("ten ants" - they have small data, ha ha!) per cluster.
Out of curiosity, how much data might a single tenant have.
If the tenants shared a data model then you could separate their data using
a tenant ID in the par
With small data size and unknown access pattern, any particular reason to
choose C*? It sounds like a relational database fits better.
On Tue, Apr 5, 2016 at 11:40 PM, jason zhao yang <
zhaoyangsingap...@gmail.com> wrote:
> Hi Jack,
>
> Thanks for the reply.
>
> Each tenant will has around 50-100
Hi Jack,
Thanks for the reply.
Each tenant will has around 50-100 tables for their applications. probably
log collection, probably account table, it's not fixed and depends on
tenants' need.
There will be a team in charge of helping tenant to do data modeling and
access patterns. Tenants will no
Thanks Kai,
One approach discussed in that post is about disabling slab allocation.
What are the consequences except for lower GC performance?
Kai Wang 于2016年4月6日周三 上午5:40写道：
> Once a while the question about table count rises in this list. The most
> recent is
> https://groups.google.com/forum
What is the nature of these tenants? Are they each creating their own data
models? Is there one central authority that will approve of all data models
and who can adjust the cluster configuration to support those models?
Generally speaking, multi-tenancy is an anti-pattern for Cassandra and for
mo
Once a while the question about table count rises in this list. The most
recent is
https://groups.google.com/forum/#!topic/nosql-databases/IblAhiLUXdk
In short C* is not designed to scale with the table count. For one each
table/CF has some fixed memory footprint on *ALL* nodes. The consensus is
y
Hi,
This is Jason.
Currently, I am using C* 2.1.10, I want to ask what's the optimal number of
tables I should create in one cluster?
My use case is that I will prepare a keyspace for each of my tenant, and
every tenant will create tables they needed. Assume each tenant created 50
tables with no
10 matches
Mail list logo
