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 6AE01112CA for ; Mon, 9 Jun 2014 10:54:50 +0000 (UTC) Received: (qmail 1633 invoked by uid 500); 9 Jun 2014 10:54:48 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 1591 invoked by uid 500); 9 Jun 2014 10:54:48 -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 1580 invoked by uid 99); 9 Jun 2014 10:54:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jun 2014 10:54:48 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of colinkuo.tw@gmail.com designates 209.85.213.179 as permitted sender) Received: from [209.85.213.179] (HELO mail-ig0-f179.google.com) (209.85.213.179) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jun 2014 10:54:45 +0000 Received: by mail-ig0-f179.google.com with SMTP id r2so1723566igi.12 for ; Mon, 09 Jun 2014 03:54:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=NCopt9IRYo2LlbCCHr3PPQmQlmru3pn6Y3++2fkhYRg=; b=KDX0t62yIp5zYgDWLuE/ye22NnMtPjlqB62rFyRYBgkQGBSdKwGZ45VkTdw+NbZgvX 6EpaddmygzVPoRGTO7qMmCcMPTxZpitDF7dU6VsijzUv5+HPG1kn+V5d5gsBGvVQMikY 3pQ9DPfzKiOB33RewgKHrJggZtf9PNYJfXSTOL+VXc/uiKzcsteE3hchHUeSxlb0Omrc Ih+iQ5leIDeVMhd2u3HH4IfhVVf7T4hiJwsyxw/8ZOnhpqMVB/fNqw5naFny4myVhCMV SN9P1IomEhjhKvT/uO8OAuJhcBCBIekLoaxIlDx8CHZ9Nv7rbmpy5cm+7C6b2MM5YDeF LmqQ== X-Received: by 10.50.98.100 with SMTP id eh4mr36552654igb.9.1402311261482; Mon, 09 Jun 2014 03:54:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.217.229 with HTTP; Mon, 9 Jun 2014 03:53:41 -0700 (PDT) In-Reply-To: References: From: Colin Kuo Date: Mon, 9 Jun 2014 18:53:41 +0800 Message-ID: Subject: Re: high pending compactions To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=047d7b2e15df9af4fe04fb650860 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b2e15df9af4fe04fb650860 Content-Type: text/plain; charset=UTF-8 As Jake suggested, you could firstly increase "compaction_throughput_mb_per_sec" and "concurrent_compactions" to suitable values if system resource is allowed. From my understanding, major compaction will internally acquire lock before running compaction. In your case, there might be a major compaction blocking the pending following compaction tasks. You could check the result of "nodetool compactionstats" and C* system log for double confirm. If the running compaction is compacting wide row for a long time, you could try to tune "in_memory_compaction_limit_in_mb" value. Thanks, On Sun, Jun 8, 2014 at 11:27 PM, S C wrote: > I am using Cassandra 1.1 (sorry bit old) and I am seeing high pending > compaction count. "pending tasks: 67" while active compaction tasks are > not more than 5. I have a 24CPU machine. Shouldn't I be seeing more > compactions? Is this a pattern of high writes and compactions backing up? > How can I improve this? Here are my thoughts. > > > 1. Increase memtable_total_space_in_mb > 2. Increase compaction_throughput_mb_per_sec > 3. Increase concurrent_compactions > > > Sorry if this was discussed already. Any pointers is much appreciated. > > Thanks, > Kumar > --047d7b2e15df9af4fe04fb650860 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
As Jake suggested, you could firstly increase "c= ompaction_throughput_mb_per_sec" and "concurrent_compactions"= ; to suitable values if system resource is allowed. From my understanding, = major compaction will internally acquire lock before running compaction. In= your case, there might be a major compaction blocking the pending followin= g compaction tasks. You could check the result of "nodetool compaction= stats" and C* system log for double confirm.

If the running compaction is compacting wide row for a = long time, you could try to tune "in_memory_compaction_limit_in_mb&quo= t; value.

Thanks,



O= n Sun, Jun 8, 2014 at 11:27 PM, S C <asf11@outlook.com> wrot= e:
I am using Cassandra 1.1 (sorry bit old) and I am see= ing high pending compaction count.=C2=A0&quo= t;pending tasks: 67" while active compaction tasks are not more than 5= . I have a 24CPU machine. Shouldn't I be seeing more compactions? Is th= is a pattern of high writes and compactions backing up? How can I improve t= his? Here are my thoughts.

  1. Increase memtabl= e_total_space_in_mb
  2. Increase = compaction_throughput_mb_per_sec
  3. Increase concurrent_compactions

Sorry i= f this was discussed already. Any pointers is much appreciated.=C2=A0

Thanks,
Kumar
<= /div>

--047d7b2e15df9af4fe04fb650860--