cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <aa...@thelastpickle.com>
Subject Re: memory issue on 1.1.0
Date Wed, 06 Jun 2012 18:56:33 GMT
use drop. 

truncate is mostly for unit tests.
A
-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com

On 7/06/2012, at 6:22 AM, Poziombka, Wade L wrote:

> I believe so.  There are no warnings on startup. 
>  
> So is there a preferred way to completely eliminate a column family?
>  
> From: Tyler Hobbs [mailto:tyler@datastax.com] 
> Sent: Wednesday, June 06, 2012 1:17 PM
> To: user@cassandra.apache.org
> Subject: Re: memory issue on 1.1.0
>  
> Just to check, do you have JNA setup correctly? (You should see a couple of log messages
about it shortly after startup.)  Truncate also performs a snapshot by default.
> 
> On Wed, Jun 6, 2012 at 12:38 PM, Poziombka, Wade L <wade.l.poziombka@intel.com>
wrote:
> However, after all the work I issued a truncate on the old column family (the one replaced
by this process) and I get an out of memory condition then.
> 
> 
> 
> -- 
> Tyler Hobbs
> DataStax
> 


Mime
View raw message