Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 5565 invoked from network); 1 Jun 2010 16:28:40 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Jun 2010 16:28:40 -0000 Received: (qmail 63491 invoked by uid 500); 1 Jun 2010 16:28:39 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 63469 invoked by uid 500); 1 Jun 2010 16:28:39 -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 63460 invoked by uid 99); 1 Jun 2010 16:28:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jun 2010 16:28:39 +0000 X-ASF-Spam-Status: No, hits=1.6 required=10.0 tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of isoboroff@gmail.com designates 209.85.212.44 as permitted sender) Received: from [209.85.212.44] (HELO mail-vw0-f44.google.com) (209.85.212.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jun 2010 16:28:33 +0000 Received: by vws11 with SMTP id 11so1302684vws.31 for ; Tue, 01 Jun 2010 09:28:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=o9VYuPBLhQBN3c/tCAsNPJzdeqNrqJcYbcKcybNBhOQ=; b=ElzdxiNM/M1IsviQjw0EsKlZxJ+6f0WJfNJWntG6Aw1jQECfRBRFHVME7lUgxxBV7g RR83RXbjvvDxq3dX/KbXqdBPi6HhcaagIRju1qnDed2pHrxMW1I4rWMNnvOEjPnvpZrw eLAQww1Zl3wKHsp9vUeT2JKtOfIoq39obguIo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=pobd5Fs1p3CseR8njxatTMwKwLhS7ntke68FDOr45r0MHRwegSkluaUOCnBhIFYtNh w/PoygsXUNC8E3frFziQQOlbSjf5jjtFAWALUrAYX3UV3g9OUoRN7YLzQ6m7IhX9DFuM 6ZD33iBnWV8e1LBIKx/aZOiBUx1/CWN1+vJ10= MIME-Version: 1.0 Received: by 10.224.45.22 with SMTP id c22mr2502691qaf.379.1275409680376; Tue, 01 Jun 2010 09:28:00 -0700 (PDT) Received: by 10.229.27.139 with HTTP; Tue, 1 Jun 2010 09:27:59 -0700 (PDT) Date: Tue, 1 Jun 2010 12:27:59 -0400 Message-ID: Subject: Monitoring compaction From: Ian Soboroff To: user Content-Type: multipart/alternative; boundary=00c09fa21cb4f3be530487fa7433 --00c09fa21cb4f3be530487fa7433 Content-Type: text/plain; charset=ISO-8859-1 Are stats exposed over JMX for compaction? I'm trying to see when a node is in compaction, and guess when it will complete. tpstats doesn't show anything but the process is using lots of CPU time... I was wondering if there's a better view on compaction besides looking backwards in the system.log for a compaction start message without a corresponding completion message. Ian --00c09fa21cb4f3be530487fa7433 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Are stats exposed over JMX for compaction?=A0 I'm trying to see when a = node is in compaction, and guess when it will complete.=A0 tpstats doesn= 9;t show anything but the process is using lots of CPU time... I was wonder= ing if there's a better view on compaction besides looking backwards in= the system.log for a compaction start message without a corresponding comp= letion message.

Ian

--00c09fa21cb4f3be530487fa7433--