Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of rcoli@eventbrite.com designates
 209.85.216.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <0DB802F2-9874-4D52-B2DF-4F9817F19141@thelastpickle.com>
References: <51C98DA0.1020006@gridnine.com>
	<841A5FC1-FBCB-4664-8825-CE497D9FED4F@gmail.com>
	<CAEPxca1569EtZ0qt0VWT4ZvZxFRNHNbtJ9xkMN7DE0Zqp1brvA@mail.gmail.com>
	<0DB802F2-9874-4D52-B2DF-4F9817F19141@thelastpickle.com>
Date: Thu, 27 Jun 2013 11:30:17 -0700
Message-ID: 
 <CAEDUwd3Qvvu8caLzkvqvxCyHQBUPo0LNm8VgWoo6Y-oMjiQKbg@mail.gmail.com>
Subject: Re: Cassandra as storage for cache data
From: Robert Coli <rcoli@eventbrite.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jun 26, 2013 at 9:51 PM, aaron morton <aaron@thelastpickle.com> wrote:
> WARNING: disabling durable_writes means that writes are only in memory and
> will not be committed to disk until the CF's are flushed. You should
> *always* use nodetool drain before shutting down a node in this case.

While a rational and informed observer would infer the need for drain
from the normally tight relationship of memtables to the contents of
the commit log, clean shutdown actually explicitly calls flush when
durable_writes is disabled.

https://issues.apache.org/jira/browse/CASSANDRA-2958

=Rob