You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2016/09/01 17:45:21 UTC
[jira] [Commented] (CASSANDRA-12532) Include repair id in repair
start message
[ https://issues.apache.org/jira/browse/CASSANDRA-12532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456125#comment-15456125 ]
Tyler Hobbs commented on CASSANDRA-12532:
-----------------------------------------
[~cnlwsu] ping. Just want to make sure you didn't miss this ^. The dtests that need to be updated are just the few that failed in the CI test run.
> Include repair id in repair start message
> -----------------------------------------
>
> Key: CASSANDRA-12532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12532
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Chris Lohfink
> Assignee: Chris Lohfink
> Attachments: 12532-trunk.patch
>
>
> Currently its not really possible to map the repairs command id that is returned from JMX to the id used tables in in system_traces, and system_distributed keyspaces. In the START we can just include it in the message to make it possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)