[jira] [Created] (CASSANDRA-14994) Incorrect repair history when running repair

["Marcus Olsson (JIRA)" <ji...@apache.org>]

Marcus Olsson created CASSANDRA-14994:
-----------------------------------------

             Summary: Incorrect repair history when running repair
                 Key: CASSANDRA-14994
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14994
             Project: Cassandra
          Issue Type: Bug
            Reporter: Marcus Olsson


Since CASSANDRA-5220 there is an issue with *system_distributed.repair_history* when using virtual nodes. Performing a standard "nodetool repair" will create a lot less entries than it should.

Example:

{code}
$ ccm create test_repair -n 3 --vnodes -v 3.0.17

...

cqlsh> CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 3};
cqlsh> CREATE TABLE test.test(key PRIMARY KEY);

...

ccm node1 nodetool repair test

...

cqlsh> SELECT keyspace_name, columnfamily_name, id, range_begin, range_end FROM system_distributed.repair_history ;

 keyspace_name | columnfamily_name | id                                   | range_begin         | range_end
---------------+-------------------+--------------------------------------+---------------------+---------------------
          test |              test | 12f27830-1e53-11e9-93a0-2122ff85bd0a | 6842951316968308632 | 6844625844103123572
{code}

In the above example the cluster is created with 256 tokens but the repair history only shows one entry.

The problem is that in CASSANDRA-5220 a single repair session can repair multiple token ranges but the insertion into the repair_history table is done with the same id for all of them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org