[
https://issues.apache.org/jira/browse/CASSANDRA-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Chan updated CASSANDRA-5483:
--------------------------------
Attachment: test-5483-system_traces-events.txt
[email protected]
tr...@8ebeee1-5483-v01-001-trace-filtering-and-tracestate-propagation.txt
This patch contains only the minimum necessary to get a proof-of-concept
working, but I thought I'd get some feedback before going any further.
Currently it reproduces some of the repair logs into {{system_traces.events}}.
For the simple test below, it's not too bad, but the traces seem to get large
fast as the amount of data grows. The same technique used for repair seems to
work for bootstrap and decommission with the caveat that if you try to trace
too far into the decommission process, it doesn't get propagated to the other
nodes.
For convenience:
{noformat}
# optional; patch should apply with any recent trunk
#git checkout -b 5483-repair-filtering 8ebeee1
git apply
tr...@8ebeee1-5483-v01-001-trace-filtering-and-tracestate-propagation.txt
git apply [email protected]
ant
# simple test
ccm create test-5483
ccm populate -n 3
ccm start
cat <<"EOT" | ccm node1 cqlsh
CREATE SCHEMA s1
WITH replication = { 'class' : 'SimpleStrategy', 'replication_factor' : 2 };
USE s1;
CREATE TABLE users (
user_id varchar PRIMARY KEY,
first varchar,
last varchar,
age int
);
INSERT INTO users (user_id, first, last, age)
VALUES ('jsmith', 'John', 'Smith', 42);
EOT
ccm node1 repair
cat <<"EOT" | ccm node1 cqlsh
copy system_traces.events to 'test-5483-system_traces-events.txt';
EOT
{noformat}
> Repair tracing
> --------------
>
> Key: CASSANDRA-5483
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5483
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Yuki Morishita
> Priority: Minor
> Labels: repair
> Attachments: test-5483-system_traces-events.txt,
> tr...@8ebeee1-5483-v01-001-trace-filtering-and-tracestate-propagation.txt,
> [email protected]
>
>
> 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.1.5#6160)
