cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Razi Khaja (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9266) Repair failed with error Already repairing SSTableReader(path='/path/to/keyspace/column_family/keyspace-column_family--Data.db'), can not continue.
Date Tue, 30 Jun 2015 17:06:05 GMT

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

Razi Khaja commented on CASSANDRA-9266:
---------------------------------------

I've loaded data into our new SSD cluster.  This cluster is independent of our other cluster
with spinning disks.  I have not tried incremental repair yet as the full repair using Cassandra
2.1.7 is failing.

I get the following error for every single range.  Should I open a new ticket.
{code}
[2015-06-29 20:49:52,527] Nothing to repair for keyspace 'system'
[2015-06-29 20:49:52,556] Starting repair command #1, repairing 517 ranges for keyspace megalink
(parallelism=SEQUENTIAL, full=true)
[2015-06-30 01:48:07,805] Repair session 4ec33070-1eca-11e5-b421-693057c03db8 for range (118891166778745801,147977570685436220]
failed with error org.apache.cassandra.exceptions.RepairException: [repair #4ec33070-1eca-11e5-b421-693057c03db8
on megalink/clone_taxonomy_v2, (118891166778745801,147977570685436220]] Sync failed between
/ip_for_cass124 and /ip_for_cass125,126,126
:
:
:
{code}

{code}
Datacenter: DC4
==================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address                          Load       Tokens  Owns    Host ID                  
            Rack
UN  cass127  654.65 GB  256     ?       366d6aa9-ec8f-4453-b5e5-13c6f934cb3c  r1
UN  cass126  646.03 GB  256     ?       0505a6ce-8ee8-4f24-8dc1-557c180dad7b  r1
UN  cass124  691.43 GB  256     ?       7a00df00-67da-4daf-9638-4be26964f4b5  r1
UN  cass125  708.42 GB  256     ?       8dd8cdd9-3b49-4fa0-a252-0212317e6193  r1

Note: Non-system keyspaces don't have the same replication settings, effective ownership information
is meaningless
{code}



> Repair failed with error Already repairing SSTableReader(path='/path/to/keyspace/column_family/keyspace-column_family--Data.db'),
can not continue.
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-9266
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9266
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Cassandra 2.1.3
>            Reporter: Razi Khaja
>            Assignee: Marcus Eriksson
>             Fix For: 2.1.x
>
>         Attachments: cassandra_system.log.partial.cass320.CASSANDRA-9266.txt, cassandra_system.log.partial.cass321.CASSANDRA-9266.txt,
cassandra_system.log.partial.cass322.CASSANDRA-9266.txt, cassandra_system.log.partial.cass323.CASSANDRA-9266.txt
>
>
> I am running incremental parallel repair using the following command:
> {code}
> nodetool --host my_hostname repair --incremental --in-local-dc --parallel
> {code}
> and get the following error:
> {code}
> Repair failed with error Already repairing SSTableReader(path='/path/to/keyspace/column_family/keyspace-column_family--Data.db'),
can not continue.
> {code}
> I have 3 data centers, each with 4 nodes. Neither incremental or full repair is running
on any of my other nodes.



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

Mime
View raw message