cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2979) Skip system table when repair
Date Sun, 31 Jul 2011 21:15:48 GMT

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

Jonathan Ellis updated CASSANDRA-2979:
--------------------------------------

             Reviewer: slebresne
    Affects Version/s:     (was: 0.8.2)
             Assignee: Norman Maurer

I could have sworn we already skip system table on repair.  Maybe that is only in trunk?

> Skip system table when repair
> -----------------------------
>
>                 Key: CASSANDRA-2979
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2979
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Norman Maurer
>            Assignee: Norman Maurer
>             Fix For: 0.8.3
>
>         Attachments: CASSANDRA-2979
>
>
> From ml:
> When I run nodetool repair on a node on my 3-node cluster, I see 3 messages like the
following:
>  INFO [manual-repair-6d9a617f-c496-4744-9002-a56909b83d5b] 2011-07-30 18:50:28,464 AntiEntropyService.java
(line 636) No neighbors to repair with for system on (0,56713727820156410577229101238628035242]:
manual-repair-6d9a617f-c496-4744-9002-a56909b83d5b completed.
> Granted, there's no data on these machines yet.  Is this normal?
> And the answer:
> You can discard those. This is saying it cannot repair the system keyspace
> (table used internally). It turns those aren't replicated and thus don't need
> to be repaired. We should probably update the code to skip trying to
> repair the system table but in the meantime this is harmless.
> --
> Sylvain

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message