Or upgrade to 1.0 and use leveled compaction
(http://www.datastax.com/dev/blog/leveled-compaction-in-apache-cassandra)
On Thu, Oct 13, 2011 at 4:28 PM, aaron morton wrote:
> They only have a minimum time, gc_grace_seconds for deletes.
>
> If you want to be really watch disk space reduce the compa
They only have a minimum time, gc_grace_seconds for deletes.
If you want to be really watch disk space reduce the compaction thresholds on
the CF.
Or run a major compaction as part of maintenance.
cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.the
durable_writes sounds great - thank you! I really do not need commit log
here.
Another question: it is possible to configure live time of Tombstones?
Regards,
Maciej
> - Serializing data is not an option, because I would like to have possibility
> to access data using console
fair enough, but I would do some tests to see the difference in performance and
disk space
> - Using Cassandra to build something like "HTTP session store" with short TTL
> is not an a
- RF is 1. We have few KeySpaces, only this one is not replicated - this
data is not that very important. In case of error customer will have to
execute process again. But again, I would like to persist it.
- Serializing data is not an option, because I would like to have
possibility to access data
Some thoughts…
> non replicated Key Space
Not sure what you mean here. Do you mean RF 1 ? I would consider using 3.
Consider what happens you want to install a rolling upgrade to the cluster.
> single Column Family, where key is session ID and each column within row
> stores single key/value -
Hi *,
I would like to use Cassandra to store session related informations. I do
not have real HTTP session - it's different protocol, but the same concept.
Memcached would be fine, but I would like to additionally persist data.
Cassandra setup:
- non replicated Key Space
- single Column F
