This documentation from Datastax may be helpful to understand the purpose
of memtables and sstables.
http://docs.datastax.com/en/cassandra/2.0/cassandra/dml/dml_write_path_c.html
Ray
On Sat, Sep 5, 2015 at 10:36 AM Anuj Wadehra wrote:
> Memtables are for storing writes in memory till they are f
I have not use tablesnap but it appears that it does not necessarily depend
upon taking a cassandra snapshot. The example given in their documentation
shows the source folder as /var/lib/cassandra/data/GiantKeyspace, which is
the root of the "GiantKeyspace" keyspace. But, snapshots operate at the
c
I don't understand how the creation of a snapshot causes any load
whatsoever. By definition, a snapshot is a hard link of an existing
SSTable. The SSTable is not being physically copied so there is no disk
I/O, it's just a reference to an inode.
--
Ray //o-o\\
On Tue, Nov 5, 2013 at 8:09 PM, A
Your quotes need to be escaped:
python -c "num=2; print \"\n\".join([(\"token %d: %d\"
%(i,(i*(2**127)/num))) for i in range(0,num)])"
--
Ray //o-o\\
On Fri, Nov 1, 2013 at 10:36 AM, Peter Sanford
wrote:
> I can't tell you why that one-liner isn't working, but you can try
> http://www.cassan
