[
https://issues.apache.org/jira/browse/CASSANDRA-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177804#comment-14177804
]
Michael Shuler commented on CASSANDRA-5483:
-------------------------------------------
bq. My old method for forcing a streaming repair (yukim's "ccm clear"
suggestion) no longer seems to work.
I peeked at the ccm git repo and I don't see any recent changes around "clear".
I did not go through your whole process, but a quick test of clear works out
for me with the latest ccm HEAD:
{noformat}
mshuler@hana:~$ ccm create test -v git:cassandra-2.1.0 -n1 -s
Fetching Cassandra updates...
Current cluster is now: test
mshuler@hana:~$ ls -la ~/.ccm/test/node1/{commitlogs,data/system}/
/home/mshuler/.ccm/test/node1/commitlogs/:
total 108
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:34 .
drwxr-xr-x 8 mshuler mshuler 4096 Oct 20 20:34 ..
-rw-r--r-- 1 mshuler mshuler 33554432 Oct 20 20:35 CommitLog-4-1413855299422.log
-rw-r--r-- 1 mshuler mshuler 33554432 Oct 20 20:34 CommitLog-4-1413855299423.log
/home/mshuler/.ccm/test/node1/data/system/:
total 72
drwxr-xr-x 18 mshuler mshuler 4096 Oct 20 20:34 .
drwxr-xr-x 4 mshuler mshuler 4096 Oct 20 20:35 ..
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:34
IndexInfo-9f5c6374d48532299a0a5094af9ad1e3
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:34
batchlog-0290003c977e397cac3efdfdc01d626b
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:34
compaction_history-b4dbb7b4dc493fb5b3bfce6e434832ca
drwxr-xr-x 3 mshuler mshuler 4096 Oct 20 20:34
compactions_in_progress-55080ab05d9c388690a4acb25fe1f77b
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:34
hints-2666e20573ef38b390fefecf96e8f0c7
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:35
local-7ad54392bcdd35a684174e047860b377
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:34
paxos-b7b7f0c2fd0a34108c053ef614bb7c2d
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:34
peer_events-59dfeaea8db2334191ef109974d81484
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:34
peers-37f71aca7dc2383ba70672528af04d4f
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:34
range_xfers-55d764384e553f8b9f6e676d4af3976d
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:35
schema_columnfamilies-45f5b36024bc3f83a3631034ea4fa697
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:35
schema_columns-296e9c049bec3085827dc17d3df2122a
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:35
schema_keyspaces-b0f2235744583cdb9631c43e59ce3676
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:34
schema_triggers-0359bc7171233ee19a4ab9dfb11fc125
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:34
schema_usertypes-3aa752254f82350b8d5c430fa221fa0a
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:34
sstable_activity-5a1ff267ace03f128563cfae6103c65e
mshuler@hana:~$ ccm node1 clear
mshuler@hana:~$ ls -la ~/.ccm/test/node1/{commitlogs,data/system}/
ls: cannot access /home/mshuler/.ccm/test/node1/data/system/: No such file or
directory
/home/mshuler/.ccm/test/node1/commitlogs/:
total 8
drwxr-xr-x 2 mshuler mshuler 4096 Oct 20 20:35 .
drwxr-xr-x 8 mshuler mshuler 4096 Oct 20 20:35 ..
{noformat}
[~philipthompson] do you know of any recent changes around "clear"?
> 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-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,
> 5483-v08-11-Shorten-trace-messages.-Use-Tracing-begin.patch,
> 5483-v08-12-Trace-streaming-in-Differencer-StreamingRepairTask.patch,
> 5483-v08-13-sendNotification-of-local-traces-back-to-nodetool.patch,
> 5483-v08-14-Poll-system_traces.events.patch,
> 5483-v08-15-Limit-trace-notifications.-Add-exponential-backoff.patch,
> 5483-v09-16-Fix-hang-caused-by-incorrect-exit-code.patch,
> 5483-v10-17-minor-bugfixes-and-changes.patch,
> 5483-v10-rebased-and-squashed-471f5cc.patch, 5483-v11-01-squashed.patch,
> 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-squashed.patch,
> 5483-v15-02-Hook-up-exponential-backoff-functionality.patch,
> 5483-v15-03-Exact-doubling-for-exponential-backoff.patch,
> 5483-v15-04-Re-add-old-StorageService-JMX-signatures.patch,
> 5483-v15-05-Move-command-column-to-system_traces.sessions.patch,
> 5483-v15.patch, 5483-v17.patch, ccm-repair-test,
> cqlsh-left-justify-text-columns.patch, prerepair-vs-postbuggedrepair.diff,
> 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.3.4#6332)
