On Wed, Apr 30, 2014 at 5:36 PM, Michael Shuler wrote:
> For the benefit of the ML, CASSANDRA-7127 was opened, and snapshots will
> not be taken, if conf/cassandra.yaml has:
>
> auto_snapshot: false
>
Didn't this already exist as a (not-in-the-default-conf-file) option? I was
aware of it (somethi
On 04/30/2014 05:29 PM, Robert Coli wrote:
On Wed, Apr 30, 2014 at 3:25 PM, Batranut Bogdan mailto:batra...@yahoo.com>> wrote:
During the development of our entire system we generated huge tables
(GB or TB) then had to drop them since we changed the definition.
This takes up space. T
On Wed, Apr 30, 2014 at 3:25 PM, Batranut Bogdan wrote:
> During the development of our entire system we generated huge tables (GB
> or TB) then had to drop them since we changed the definition. This takes up
> space. There is a constant write on the system so we want to optimize our
> cluster. B
Well this is not good at all...
During the development of our entire system we generated huge tables (GB or TB)
then had to drop them since we changed the definition. This takes up space.
There is a constant write on the system so we want to optimize our cluster.
Basicaly not expanding untill t
On Wed, Apr 30, 2014 at 3:00 PM, Batranut Bogdan wrote:
> Is there a way to get cassandra to remove these old and unused tables?
>
Those directories have to exist after DROP because snapshots taken when you
drop, and the snapshots are in a subdirectory of those directories.
nodetool clearsnapsh
Hello all,
I have a question.
I looked in the keyspace directory and saw that old dirs still exist after
dropping the corresponding table.
eg drop table t1 and in /data/keyspace I still see the t1 dir.
Is there a way to get cassandra to remove these old and unused tables?
