Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EAAB09B5E for ; Sun, 20 Nov 2011 21:54:46 +0000 (UTC) Received: (qmail 82290 invoked by uid 500); 20 Nov 2011 21:54:44 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 82263 invoked by uid 500); 20 Nov 2011 21:54:44 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 82255 invoked by uid 99); 20 Nov 2011 21:54:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Nov 2011 21:54:44 +0000 X-ASF-Spam-Status: No, hits=1.6 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of md.jahangir27@gmail.com designates 209.85.161.44 as permitted sender) Received: from [209.85.161.44] (HELO mail-fx0-f44.google.com) (209.85.161.44) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Nov 2011 21:54:39 +0000 Received: by fabs1 with SMTP id s1so1011214fab.31 for ; Sun, 20 Nov 2011 13:54:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=sBeIR/tDgz89s1S38Du5SW/KVmzqtd/CNorEQgSbcBI=; b=HmiPxHsg4/VkMpahfn5P41W8w66HyJvaYUY84hiSj+tD7JyJ9810HhYc25dWSmCAqV 5+bMI+uEOhtAnmD+FPUzLkcPiS7sRXknVDw02PNPB0DWZhZ/y2aF10jqiRYt8k8XslEU xr2/evwVsxiyaIvZRjphvVJXXJmUMAepIXlHg= MIME-Version: 1.0 Received: by 10.152.103.51 with SMTP id ft19mr7323856lab.42.1321826058333; Sun, 20 Nov 2011 13:54:18 -0800 (PST) Received: by 10.152.20.165 with HTTP; Sun, 20 Nov 2011 13:54:18 -0800 (PST) Received: by 10.152.20.165 with HTTP; Sun, 20 Nov 2011 13:54:18 -0800 (PST) In-Reply-To: <4EC54BE9.1000605@bnl.gov> References: <4EC54BE9.1000605@bnl.gov> Date: Sun, 20 Nov 2011 16:54:18 -0500 Message-ID: Subject: Re: What sort of load do the tombstones create on the cluster? From: Jahangir Mohammed To: user@cassandra.apache.org, potekhin@bnl.gov Content-Type: multipart/alternative; boundary=f46d04083d9fa96ed604b2319c84 --f46d04083d9fa96ed604b2319c84 Content-Type: text/plain; charset=ISO-8859-1 Mostly, they are I/O and CPU intensive during major compaction. If ganglia doesn't have anything suspicious there, then what is performance loss ? Read or write? On Nov 17, 2011 1:01 PM, "Maxim Potekhin" wrote: > In view of my unpleasant discovery last week that deletions in Cassandra > lead to a very real > and serious performance loss, I'm working on a strategy of moving forward. > > If the tombstones do cause such problem, where should I be looking for > performance bottlenecks? > Is it disk, CPU or something else? Thing is, I don't see anything > outstanding in my Ganglia plots. > > TIA, > > Maxim > > --f46d04083d9fa96ed604b2319c84 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Mostly, they are I/O and CPU intensive during major compaction. If gangl= ia doesn't have anything suspicious there, then what is performance los= s ? Read or write?

On Nov 17, 2011 1:01 PM, "Maxim Potekhin&qu= ot; <potekhin@bnl.gov> wrote:=
In view of my unpleasant discovery last week that deletions in Cassandra le= ad to a very real
and serious performance loss, I'm working on a strategy of moving forwa= rd.

If the tombstones do cause such problem, where should I be looking for perf= ormance bottlenecks?
Is it disk, CPU or something else? Thing is, I don't see anything outst= anding in my Ganglia plots.

TIA,

Maxim

--f46d04083d9fa96ed604b2319c84--