Could you please tell me why?
There might be pending sstable removals on disk, which won't happen
until GC or restart. If you just did a bulk insert and checked
diskspace immediately afterwards, I think this is a possible
explanation.
(See Write path on
I'm fairly certain the write path hits the commit log first, then the
memtable.
I didn't mean to imply an ordering between the two (I probably should
not have said memtable plus commit log...), and yes I believe so.
--
/ Peter Schuller aka scode
Not sure if this was mentioned, but MongoDB is strongly consistent while
Cassandra is eventually consistent -- at least about a month ago when I
looked at it in more detail, though with vector clocks in 0.7, this may be
less of an issue.
Did Mongo switch away from the fsync() every now and
The biggest impact on your write performance will most likely be the
consistency level of your writes. In other words, how many nodes you want to
wait for before you acknowledge the write back to the client.
I believe the consistency level is only expected to have a significant
impact on
what is the benefit of creating bloom filter when cassandra writes data, how
does it helps ?
It allows Cassandra to answer requests for non-existent keys without
going to disk, except in cases where the bloom filter gives a false
positive.
See:
