Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4CBE01751B for ; Tue, 7 Oct 2014 17:15:37 +0000 (UTC) Received: (qmail 61609 invoked by uid 500); 7 Oct 2014 17:15:37 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 61576 invoked by uid 500); 7 Oct 2014 17:15:37 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 61563 invoked by uid 99); 7 Oct 2014 17:15:37 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Oct 2014 17:15:37 +0000 Date: Tue, 7 Oct 2014 17:15:37 +0000 (UTC) From: "Joshua McKenzie (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-5483) Repair tracing MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-5483?page=3Dcom.atla= ssian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua McKenzie updated CASSANDRA-5483: --------------------------------------- Fix Version/s: 3.0 > Repair tracing > -------------- > > Key: CASSANDRA-5483 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5483 > Project: Cassandra > Issue Type: Improvement > Components: Tools > Reporter: Yuki Morishita > Assignee: Ben Chan > Priority: Minor > Labels: repair > Fix For: 3.0 > > Attachments: 5483-full-trunk.txt, 5483-v06-04-Allow-tracing-ttl-t= o-be-configured.patch, 5483-v06-05-Add-a-command-column-to-system_traces.ev= ents.patch, 5483-v06-06-Fix-interruption-in-tracestate-propagation.patch, 5= 483-v07-07-Better-constructor-parameters-for-DebuggableThreadPoolExecutor.p= atch, 5483-v07-08-Fix-brace-style.patch, 5483-v07-09-Add-trace-option-to-a-= more-complete-set-of-repair-functions.patch, 5483-v07-10-Correct-name-of-bo= olean-repairedAt-to-fullRepair.patch, 5483-v08-11-Shorten-trace-messages.-U= se-Tracing-begin.patch, 5483-v08-12-Trace-streaming-in-Differencer-Streamin= gRepairTask.patch, 5483-v08-13-sendNotification-of-local-traces-back-to-nod= etool.patch, 5483-v08-14-Poll-system_traces.events.patch, 5483-v08-15-Limit= -trace-notifications.-Add-exponential-backoff.patch, 5483-v09-16-Fix-hang-c= aused-by-incorrect-exit-code.patch, 5483-v10-17-minor-bugfixes-and-changes.= patch, 5483-v10-rebased-and-squashed-471f5cc.patch, 5483-v11-01-squashed.pa= tch, 5483-v11-squashed-nits.patch, 5483-v12-02-cassandra-yaml-ttl-doc.patch= , 5483-v13-608fb03-May-14-trace-formatting-changes.patch, 5483-v14-01-squas= hed.patch, 5483-v15-02-Hook-up-exponential-backoff-functionality.patch, 548= 3-v15-03-Exact-doubling-for-exponential-backoff.patch, 5483-v15-04-Re-add-o= ld-StorageService-JMX-signatures.patch, 5483-v15-05-Move-command-column-to-= system_traces.sessions.patch, 5483-v15.patch, ccm-repair-test, cqlsh-left-j= ustify-text-columns.patch, prerepair-vs-postbuggedrepair.diff, test-5483-sy= stem_traces-events.txt, trunk@4620823-5483-v02-0001-Trace-filtering-and-tra= cestate-propagation.patch, trunk@4620823-5483-v02-0002-Put-a-few-traces-par= allel-to-the-repair-logging.patch, trunk@8ebeee1-5483-v01-001-trace-filteri= ng-and-tracestate-propagation.txt, trunk@8ebeee1-5483-v01-002-simple-repair= -tracing.txt, v02p02-5483-v03-0003-Make-repair-tracing-controllable-via-nod= etool.patch, v02p02-5483-v04-0003-This-time-use-an-EnumSet-to-pass-boolean-= repair-options.patch, v02p02-5483-v05-0003-Use-long-instead-of-EnumSet-to-w= ork-with-JMX.patch > > > I think it would be nice to log repair stats and results like query traci= ng stores traces to system keyspace. With it, you don't have to lookup each= log file to see what was the status and how it performed the repair you in= voked. Instead, you can query the repair log with session ID to see the sta= te and stats of all nodes involved in that repair session. -- This message was sent by Atlassian JIRA (v6.3.4#6332)