Hi Eric,
Zitat von Eric Stevens :
@Jens,
will "inactive" CFs be released from C*'s memory after i.e. a few days
or when under resource pressure?
No, certain memory structures are allocated and will remain resident on
each node for as long as the table exists.
That's good to know, while not
@Jens,
> will "inactive" CFs be released from C*'s memory after i.e. a few days
> or when under resource pressure?
No, certain memory structures are allocated and will remain resident on
each node for as long as the table exists.
> These CFs are used as "time buckets", but are to be kept for spe
I would suggest that dynamic table creation is, in general, not a great idea,
regardless of the database. I would seriously consider altering your approach
to use a fixed set of tables.
On Nov 28, 2014, at 1:53 AM, Marcus Olsson
mailto:marcus.ols...@ericsson.com>> wrote:
Hi,
We encountered th
Hi,
We encountered the same problem and created a JIRA for it:
https://issues.apache.org/jira/browse/CASSANDRA-8387 .
/Marcus O
On 11/27/2014 04:19 PM, DuyHai Doan wrote:
Hello Peter
For safe concurrent table creation, use CREATE TABLE xxx IF NOT
EXISTS. It will use light weight transacti
Hi DuyHai,
Zitat von DuyHai Doan :
Hello Peter
I'm working with Peter and am the one initiating the table creation in
my code.
For safe concurrent table creation, use CREATE TABLE xxx IF NOT EXISTS. It
unfortunately, my code already has the "IF NOT EXISTS" clause in the
create stateme
Hi Eric,
Zitat von Eric Stevens :
Be careful with creating many dynamically created column families unless
you're cleaning up old ones to keep the total number of CF's reasonable.
Having many column families will increase memory pressure and reduce
overall performance.
will "inactive" CFs be r
Be careful with creating many dynamically created column families unless
you're cleaning up old ones to keep the total number of CF's reasonable.
Having many column families will increase memory pressure and reduce
overall performance.
On Thu Nov 27 2014 at 8:19:35 AM DuyHai Doan wrote:
> Hello
Hello Peter
For safe concurrent table creation, use CREATE TABLE xxx IF NOT EXISTS. It
will use light weight transaction and you'll have to pay some penalty in
term of performance but at least the table creation will be linearizable
Le 27 nov. 2014 14:26, "Peter Lange" a écrit :
> Hi,
>
> We use
Hi,
We use a four-node Cassandra-Cluster in Version 2.1.2. Our
Client-Applications creates Tables dynamically. At one point two (or
more) of our Clients connected to two (or more) different
Cassandra-Nodes will create the same table simultaneously. We get the
"Column family ID mismatch"-E
