cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8511) repairedAt value is no longer logged
Date Fri, 26 Feb 2016 17:22:18 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169356#comment-15169356
] 

Philip Thompson commented on CASSANDRA-8511:
--------------------------------------------

The test in question is gone, but I've just checked locally, and this value is still no longer
logged. It can be recovered with sstablemetadata, however.

> repairedAt value is no longer logged
> ------------------------------------
>
>                 Key: CASSANDRA-8511
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8511
>             Project: Cassandra
>          Issue Type: Improvement
>         Environment: OSX and Ubuntu
>            Reporter: Philip Thompson
>            Priority: Minor
>              Labels: lhf
>             Fix For: 2.1.x
>
>
> The dtest repair_compaction.py is failing, which led me to discover that the repairedAt
value for sstables is no longer being logged during repair sessions, even in DEBUG logging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message