[jira] [Updated] (CASSANDRA-8694) Repair of empty keyspace hangs rather than ignoring the request
[ https://issues.apache.org/jira/browse/CASSANDRA-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Jirsa updated CASSANDRA-8694: -- Attachment: cass-8694.patch Repair of empty keyspace hangs rather than ignoring the request --- Key: CASSANDRA-8694 URL: https://issues.apache.org/jira/browse/CASSANDRA-8694 Project: Cassandra Issue Type: Bug Reporter: Ryan McGuire Priority: Minor Attachments: cass-8694.patch Create a two node cluster, create a keyspace, don't create any tables. Initiate a repair: {code} 04:32 PM:~$ ccm create -v git:cassandra-2.1 test -n 2 -s Fetching Cassandra updates... Current cluster is now: test 04:33 PM:~$ ccm node1 cqlsh Connected to test at 127.0.0.1:9042. [cqlsh 5.0.1 | Cassandra 2.1.2-SNAPSHOT | CQL spec 3.2.0 | Native protocol v3] Use HELP for help. cqlsh create KEYSPACE test WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 2}; cqlsh 04:34 PM:~$ ccm node1 nodetool -- repair [2015-01-27 16:34:11,741] Nothing to repair for keyspace 'system' [2015-01-27 16:34:11,748] Starting repair command #1, repairing 2 ranges for keyspace test (parallelism=SEQUENTIAL, full=true) {code} The repair hangs. Do the same thing but add a table, and the repair completes very quickly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-8694) Repair of empty keyspace hangs rather than ignoring the request
[ https://issues.apache.org/jira/browse/CASSANDRA-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-8694: Reviewer: Yuki Morishita Assignee: Jeff Jirsa Repair of empty keyspace hangs rather than ignoring the request --- Key: CASSANDRA-8694 URL: https://issues.apache.org/jira/browse/CASSANDRA-8694 Project: Cassandra Issue Type: Bug Reporter: Ryan McGuire Assignee: Jeff Jirsa Priority: Minor Attachments: cass-8694.patch Create a two node cluster, create a keyspace, don't create any tables. Initiate a repair: {code} 04:32 PM:~$ ccm create -v git:cassandra-2.1 test -n 2 -s Fetching Cassandra updates... Current cluster is now: test 04:33 PM:~$ ccm node1 cqlsh Connected to test at 127.0.0.1:9042. [cqlsh 5.0.1 | Cassandra 2.1.2-SNAPSHOT | CQL spec 3.2.0 | Native protocol v3] Use HELP for help. cqlsh create KEYSPACE test WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 2}; cqlsh 04:34 PM:~$ ccm node1 nodetool -- repair [2015-01-27 16:34:11,741] Nothing to repair for keyspace 'system' [2015-01-27 16:34:11,748] Starting repair command #1, repairing 2 ranges for keyspace test (parallelism=SEQUENTIAL, full=true) {code} The repair hangs. Do the same thing but add a table, and the repair completes very quickly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-8694) Repair of empty keyspace hangs rather than ignoring the request
[ https://issues.apache.org/jira/browse/CASSANDRA-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McGuire updated CASSANDRA-8694: Reproduced In: 2.1.2 Repair of empty keyspace hangs rather than ignoring the request --- Key: CASSANDRA-8694 URL: https://issues.apache.org/jira/browse/CASSANDRA-8694 Project: Cassandra Issue Type: Bug Reporter: Ryan McGuire Priority: Minor Create a two node cluster, create a keyspace, don't create any tables. Initiate a repair: {code} 04:32 PM:~$ ccm create -v git:cassandra-2.1 test -n 2 -s Fetching Cassandra updates... Current cluster is now: test 04:33 PM:~$ ccm node1 cqlsh Connected to test at 127.0.0.1:9042. [cqlsh 5.0.1 | Cassandra 2.1.2-SNAPSHOT | CQL spec 3.2.0 | Native protocol v3] Use HELP for help. cqlsh create KEYSPACE test WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 2}; cqlsh 04:34 PM:~$ ccm node1 nodetool -- repair [2015-01-27 16:34:11,741] Nothing to repair for keyspace 'system' [2015-01-27 16:34:11,748] Starting repair command #1, repairing 2 ranges for keyspace test (parallelism=SEQUENTIAL, full=true) {code} The repair hangs. Do the same thing but add a table, and the repair completes very quickly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)