cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lyuben Todorov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5351) Avoid repairing already-repaired data by default
Date Mon, 23 Dec 2013 19:54:52 GMT

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

Lyuben Todorov updated CASSANDRA-5351:
--------------------------------------

    Attachment: node3_v2_full.log
                node1_v2_full.log
                node2_v2_full.log

Attaching full logs for all 3 nodes with logging set to DEBUG. 1st repair was on node 3, and
2nd repair was on node 2. 

Nodetool output: 

{noformat}
lyubent:bin lyubentodorov$ ./nodetool repair -p 7300
[2013-12-23 21:46:38,321] Nothing to repair for keyspace 'system'
[2013-12-23 21:46:38,326] Starting repair command #1, repairing 2 ranges for keyspace test
[2013-12-23 21:46:39,536] Repair session f000e4b0-6c0a-11e3-acbf-975f903ccf5a for range (-3074457345618258603,3074457345618258602]
finished
[2013-12-23 21:46:39,541] Repair session f075c690-6c0a-11e3-acbf-975f903ccf5a for range (-9223372036854775808,-3074457345618258603]
finished
[2013-12-23 21:46:39,541] Repair command #1 finished
[2013-12-23 21:46:39,549] Starting repair command #2, repairing 2 ranges for keyspace system_traces
[2013-12-23 21:46:39,811] Repair session f0babed0-6c0a-11e3-acbf-975f903ccf5a for range (-3074457345618258603,3074457345618258602]
finished
[2013-12-23 21:46:39,816] Repair session f0cebc00-6c0a-11e3-acbf-975f903ccf5a for range (-9223372036854775808,-3074457345618258603]
finished
[2013-12-23 21:46:39,816] Repair command #2 finished
lyubent:bin lyubentodorov$ ./nodetool repair -p 7200
[2013-12-23 21:47:08,115] Nothing to repair for keyspace 'system'
[2013-12-23 21:47:08,121] Starting repair command #1, repairing 2 ranges for keyspace test
[2013-12-23 21:47:08,604] Repair session 01c2cab0-6c0b-11e3-8300-975f903ccf5a for range (-9223372036854775808,-3074457345618258603]
finished
{noformat}

> Avoid repairing already-repaired data by default
> ------------------------------------------------
>
>                 Key: CASSANDRA-5351
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5351
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Lyuben Todorov
>              Labels: repair
>             Fix For: 2.1
>
>         Attachments: node1.log, node1_v2_full.log, node2.log, node2_v2_full.log, node3.log,
node3_v2_full.log
>
>
> Repair has always built its merkle tree from all the data in a columnfamily, which is
guaranteed to work but is inefficient.
> We can improve this by remembering which sstables have already been successfully repaired,
and only repairing sstables new since the last repair.  (This automatically makes CASSANDRA-3362
much less of a problem too.)
> The tricky part is, compaction will (if not taught otherwise) mix repaired data together
with non-repaired.  So we should segregate unrepaired sstables from the repaired ones.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message