cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <aa...@thelastpickle.com>
Subject Re: Frequency of Flushing in 1.0
Date Sun, 26 Feb 2012 20:18:15 GMT
Nathan Milford has a post about taking a node down 

http://blog.milford.io/2011/11/rolling-upgrades-for-cassandra/

The only thing I would do differently would be turn off thrift first.

Cheers


-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com

On 27/02/2012, at 4:35 AM, Edward Capriolo wrote:

> If you are doing a planned maintenance you can flush first as well
> ensuring the that the commit logs will not be as large.
> 
> On Sun, Feb 26, 2012 at 10:09 AM, Radim Kolar <hsn@sendmail.cz> wrote:
>>> if a node goes down, it will take longer for commitlog replay.
>> 
>> commit log replay time is insignificant. most time during node startup is
>> wasted on index sampling. Index sampling here runs for about 15 minutes.


Mime
View raw message