Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 11 Mar 2014 19:38:46 +0000 (UTC)
From: "Ben Chan (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12642807.1366143722698.46181.1394566726320@arcas>
In-Reply-To: <JIRA.12642807.1366143722698@arcas>
References: <JIRA.12642807.1366143722698@arcas>
Subject: [jira] [Updated] (CASSANDRA-5483) Repair tracing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CASSANDRA-5483?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ben Chan updated CASSANDRA-5483:
--------------------------------

    Attachment: 5483-v07-10-Correct-name-of-boolean-repairedAt-to-fullRepai=
r.patch
                5483-v07-09-Add-trace-option-to-a-more-complete-set-of-repa=
ir-functions.patch
                5483-v07-08-Fix-brace-style.patch
                5483-v07-07-Better-constructor-parameters-for-DebuggableThr=
eadPoolExecutor.patch

> 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
>         Attachments: 5483-v06-04-Allow-tracing-ttl-to-be-configured.patch=
, 5483-v06-05-Add-a-command-column-to-system_traces.events.patch, 5483-v06-=
06-Fix-interruption-in-tracestate-propagation.patch, 5483-v07-07-Better-con=
structor-parameters-for-DebuggableThreadPoolExecutor.patch, 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-boolean-repairedAt-to-f=
ullRepair.patch, ccm-repair-test, test-5483-system_traces-events.txt, trunk=
@4620823-5483-v02-0001-Trace-filtering-and-tracestate-propagation.patch, tr=
unk@4620823-5483-v02-0002-Put-a-few-traces-parallel-to-the-repair-logging.p=
atch, trunk@8ebeee1-5483-v01-001-trace-filtering-and-tracestate-propagation=
.txt, trunk@8ebeee1-5483-v01-002-simple-repair-tracing.txt, v02p02-5483-v03=
-0003-Make-repair-tracing-controllable-via-nodetool.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-work-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.2#6252)