You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2016/03/17 11:17:33 UTC
[jira] [Resolved] (CASSANDRA-8511) repairedAt value is no longer
logged
[ https://issues.apache.org/jira/browse/CASSANDRA-8511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Eriksson resolved CASSANDRA-8511.
----------------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 2.1.x)
Not sure why the test needed repaired_at in the logs for. But if any future test needs it, we can indeed either get it from sstablemetadata or store it in system_distributed.repair_history
> 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
>
> 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)