Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: error (athena.apache.org: local policy)
From: Jan Algermissen <jan.algermissen@nordsc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: One node out of three not flushing memtables
Message-Id: <197D9A73-6FA2-4ED5-A05C-065F20B80FCF@nordsc.com>
Date: Tue, 10 Sep 2013 02:11:01 +0200
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))

I have a strange pattern: In a cluster with three equally dimensioned =
and configured nodes I keep loosing one because apparently it fails to =
flush its memtables:

http://twitpic.com/dcrtel


It is a different node every time.

So far I understand that I should expect to see the chain-saw graph when =
memtables are build up and then get flushed. But what about that third =
node? Has anyone seen something similar?

Jan

C* dsc 2.0 ,  3x 4GB, 2CPU nodes with heavy writes of 70 col-rows (aprox =
10 of those rows per wide row)

I have turned off caches, reduced overall memtable and set flush-wroters =
to 2,  rpc_reader and writer threads to 1.