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] [Commented] (CASSANDRA-11203) nodetool repair not performing repair or being incorrectly triggered in 3.0.3
Date Mon, 22 Feb 2016 13:33:18 GMT

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

Jason Kania commented on CASSANDRA-11203:
-----------------------------------------

Thanks for the suggestion. The problem persists even with the -full option used.

root@marble:/var/lib/cassandra/data/sensordb/periodicReading# nodetool repair -full
[2016-02-22 08:30:46,026] Nothing to repair for keyspace 'sensordb'
[2016-02-22 08:30:46,034] Nothing to repair for keyspace 'system_auth'
[2016-02-22 08:30:46,062] Starting repair command #5, repairing keyspace system_traces with
repair options (parallelism: parallel, primary range: false, incremental: false, job threads:
1, ColumnFamilies: [], dataCenters: [], hosts: [], # of ranges: 256)
[2016-02-22 08:30:48,317] Repair completed successfully
[2016-02-22 08:30:48,325] Repair command #5 finished in 2 seconds
root@marble:/var/lib/cassandra/data/sensordb/periodicReading# nodetool repair -full
[2016-02-22 08:30:54,838] Nothing to repair for keyspace 'sensordb'
[2016-02-22 08:30:54,845] Nothing to repair for keyspace 'system_auth'
[2016-02-22 08:30:54,879] Starting repair command #6, repairing keyspace system_traces with
repair options (parallelism: parallel, primary range: false, incremental: false, job threads:
1, ColumnFamilies: [], dataCenters: [], hosts: [], # of ranges: 256)
[2016-02-22 08:30:56,763] Repair completed successfully
[2016-02-22 08:30:56,764] Repair command #6 finished in 1 second



> 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