cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12532) Include repair id in repair start message
Date Thu, 22 Sep 2016 19:13:20 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-12532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tyler Hobbs updated CASSANDRA-12532:
------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.10
           Status: Resolved  (was: Awaiting Feedback)

The dtest has been merged, so I've committed this as {{c92928bb9c2441254b51e2ea4dc742c9245b9f4c}}
to trunk.  Thanks!

> 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
>             Fix For: 3.10
>
>         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)

Mime
View raw message