> About 80% of these CFs should be truncated every day and if we decrease many
> CF by creating one key field in one CF, a huge amount of tombstones will
> appear.
>
>
Truncation requires that all nodes be available, so if you are doing it each
day you may run into troubles if a node it down.
On Mon, Apr 29, 2013 at 12:33 AM, Sasha Yanushkevich wrote:
> 1) We’ve tested 100 threads in parallel and each thread created 10 tables.
With this pattern of creating CFs, you are begging for schema desynch.
If this actually works any meaningful percentage of the time in modern
cassandra, I would
1) We’ve tested 100 threads in parallel and each thread created 10
tables. I think we will change our data model, but another problem may
occur. About 80% of these CFs should be truncated every day and if we
decrease many CF by creating one key field in one CF, a huge amount of
tombstones will appe
> At first many CF are being created in parallel (about 1000 CF).
>
>
Can you explain this in a bit more detail ? By in parallel do you mean multiple
threads creating CF's at the same time ?
I would also recommend taking a second look at your data model, you probably do
not want to create so m
Hi All
We are testing Cassandra 1.2.3 (3 nodes with RF:2) with
FluentCassandra driver. At first many CF are being created in parallel
(about 1000 CF). After creation is done follows many insertions of
little amount of data into the DB. During tests we're receiving some
exceptions from driver, e.g.
