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 5964E178B7 for ; Thu, 19 Mar 2015 17:31:14 +0000 (UTC) Received: (qmail 57177 invoked by uid 500); 19 Mar 2015 17:30:59 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 57132 invoked by uid 500); 19 Mar 2015 17:30:59 -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 57122 invoked by uid 99); 19 Mar 2015 17:30:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Mar 2015 17:30:58 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of ianrose@fullstory.com does not designate 209.85.192.45 as permitted sender) Received: from [209.85.192.45] (HELO mail-qg0-f45.google.com) (209.85.192.45) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Mar 2015 17:30:33 +0000 Received: by qgez64 with SMTP id z64so71417898qge.2 for ; Thu, 19 Mar 2015 10:30:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=8XXRtBVNMOLSqBmI7/yvrxt2Hc68IwfGJZGIo3Dcy+Q=; b=HLIxxlRiKS8qQdc53RIYdsl/xRbIsf6PF1sCwaIvqnBhiRO6T1msFU1soVv2svZnSk 02LJ//wECUEE1wS2p2/XiI7SGgWm9bvbD3NSps+hedGqEEc0aVsY+caSy+AFo3aE6ldy 1duhllNxd8RnZCBsGZCYrBJn8Vgu58AVCogw5HQ9+6WhiqacXei5feTQxHS3Yb9IWGim LJHKYdosRececjLA6w8yTr3vYeg2Ocvy0ohhKFv6z6mOnRxdY8Rc0aoemX9/tKIp5gOM rebinXbC1E4TxX2Go125YceN4BNC/Cl2Hay7+ITioxAjhBJLQmuOebHv9awTUpNmADPx GKCw== X-Gm-Message-State: ALoCoQk3ONtH0r9gIongvlTIjpn8VmTxN9WOihpncnzyFQCQHH7pCcWUFrq3YQoEbkmGB0WZQIi+ X-Received: by 10.55.21.66 with SMTP id f63mr125551053qkh.102.1426786231400; Thu, 19 Mar 2015 10:30:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.96.42.226 with HTTP; Thu, 19 Mar 2015 10:30:11 -0700 (PDT) From: Ian Rose Date: Thu, 19 Mar 2015 13:30:11 -0400 Message-ID: Subject: best way to measure repair times? To: user Content-Type: multipart/alternative; boundary=001a1147ecd87e4dd30511a78e10 X-Virus-Checked: Checked by ClamAV on apache.org --001a1147ecd87e4dd30511a78e10 Content-Type: text/plain; charset=UTF-8 Howdy - I'd like to (a) monitor how long my repairs are taking, and (b) know when a repair is finished so that I can take some kind of followup action. What's the best way to tackle either or both of these? Some potentially relevant details: - running community apache cassandra (not DSE) - version 2.0.13 - we currently trigger repairs via an external timer that calls forceRepairAsync on the StorageService mbean via JMX Thanks! - Ian --001a1147ecd87e4dd30511a78e10 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Howdy -

I'd like to (a) monitor how= long my repairs are taking, and (b) know when a repair is finished so that= I can take some kind of followup action.=C2=A0 What's the best way to = tackle either or both of these?

Some potentially r= elevant details:

- running community apache cassan= dra (not DSE)
- version 2.0.13
- we currently trigger r= epairs via an external timer that calls=C2=A0forceRepairAsync on the=C2=A0S= torageService mbean via JMX

Thanks!
- Ia= n

--001a1147ecd87e4dd30511a78e10--