cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Kania (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-11203) nodetool repair not performing repair or being incorrectly triggered in 3.0.3
Date Mon, 22 Feb 2016 04:45:18 GMT
Jason Kania created CASSANDRA-11203:
---------------------------------------

             Summary: nodetool repair not performing repair or being incorrectly triggered
in 3.0.3
                 Key: CASSANDRA-11203
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11203
             Project: Cassandra
          Issue Type: Bug
          Components: Tools
         Environment: debian jesse up to date content
            Reporter: Jason Kania


When nodetool repair is run, it indicates that no repair is needed on some keyspaces but on
others it attempts repair. However, when run multiple times, the output seems to indicate
that the same triggering conditions still persists that indicate a problem. Alternatively,
the output could indicate that the underlying condition has not been resolved.

root@marble:/var/lib/cassandra/data/sensordb/periodicReading# nodetool repair
[2016-02-21 23:33:10,356] Nothing to repair for keyspace 'sensordb'
[2016-02-21 23:33:10,364] Nothing to repair for keyspace 'system_auth'
[2016-02-21 23:33:10,402] Starting repair command #1, repairing keyspace system_traces with
repair options (parallelism: parallel, primary range: false, incremental: true, job threads:
1, ColumnFamilies: [], dataCenters: [], hosts: [], # of ranges: 256)
[2016-02-21 23:33:12,144] Repair completed successfully
[2016-02-21 23:33:12,157] Repair command #1 finished in 1 second
root@marble:/var/lib/cassandra/data/sensordb/periodicReading# nodetool repair
[2016-02-21 23:33:31,683] Nothing to repair for keyspace 'sensordb'
[2016-02-21 23:33:31,689] Nothing to repair for keyspace 'system_auth'
[2016-02-21 23:33:31,713] Starting repair command #2, repairing keyspace system_traces with
repair options (parallelism: parallel, primary range: false, incremental: true, job threads:
1, ColumnFamilies: [], dataCenters: [], hosts: [], # of ranges: 256)
[2016-02-21 23:33:33,324] Repair completed successfully
[2016-02-21 23:33:33,334] Repair command #2 finished in 1 second



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

Mime
View raw message