[
https://issues.apache.org/jira/browse/CASSANDRA-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934196#comment-13934196
]
Yuki Morishita edited comment on CASSANDRA-5483 at 3/13/14 10:13 PM:
---------------------------------------------------------------------
bq. Is there a simple way to create a situation where a repair requires
streaming?
The easiest way is to nuke one node after writing data to all nodes.
So, for example, you create 3 nodes cluster, create keyspace with RF=3, fill
data in, clear one node(ccm node1 clear), bring it up again, then repair.
bq. Somehow the streaming repair is getting done somewhere other than
Differencer#run.
Differencer creates StreamingRepairTask at the end which creates StreamPlan and
executes.
In order to log streaming, you can add StreamEventHandler to catch streaming
events.
For mode detail see http://wiki.apache.org/cassandra/Streaming2.
For example, BulkLoader/SSTableLoader uses StreamEvent to track progress.
was (Author: yukim):
bq. Is there a simple way to create a situation where a repair requires
streaming?
The easiest way is to nuke one node after writing data to all nodes.
So, for example, you create 3 nodes cluster, create keyspace with RF=3, fill
data in, clear one node(ccm node1 clear), bring it up again, then repair.
> 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-full-trunk.txt,
> 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-constructor-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-fullRepair.patch,
> ccm-repair-test, cqlsh-left-justify-text-columns.patch,
> test-5483-system_traces-events.txt,
> trunk@4620823-5483-v02-0001-Trace-filtering-and-tracestate-propagation.patch,
> trunk@4620823-5483-v02-0002-Put-a-few-traces-parallel-to-the-repair-logging.patch,
> tr...@8ebeee1-5483-v01-001-trace-filtering-and-tracestate-propagation.txt,
> [email protected],
> 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 tracing
> 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 invoked.
> Instead, you can query the repair log with session ID to see the state and
> stats of all nodes involved in that repair session.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
