cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Spriegel (Created) (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-3369) AssertionError when adding a node and doing repair, repair hangs
Date Sun, 16 Oct 2011 16:36:11 GMT
AssertionError when adding a node and doing repair, repair hangs

                 Key: CASSANDRA-3369
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.0.0
         Environment: Ubuntu Linux amd64, 1.0.0-rc2
            Reporter: Christian Spriegel

Hi again,

I was playing aroung with Cassandra 1.0.0-rc2 and got an AssertionError. The cluster I set
up was two cassandra nodes on one laptop using different 127.0.0.* loopback devices. Both
nodes have separate folders on the harddisk.

Here is what I did:

1. Started node1 and inserted some data into it using a simple singlethreaded testprogram
(uses hector 0.8.0-2):       datacenter1 rack1       Up     Normal  583.55 MB       100.00% Token(bytes[63e5b6995466cd3221cba16646ae19ed])

2. I started another node, node 2 =       datacenter1 rack1       Up     Normal  147.57 KB       50.00%  Token(bytes[4d6ccfeaa8bb59551751a2816fde9343])       datacenter1 rack1       Up     Normal  583.55 MB       50.00%  Token(bytes[63e5b6995466cd3221cba16646ae19ed])

3. I triggered a "nodetool -h  repair" on the first node that had the data from
my test.

This repair does not seem to ever end. The nodetool is hanging now but my computer is idle.
I get an AssertionError on the first node:
	at org.apache.cassandra.service.AntiEntropyService$Validator.prepare(
	at org.apache.cassandra.db.compaction.CompactionManager.doValidationCompaction(
	at org.apache.cassandra.db.compaction.CompactionManager.access$600(
	at org.apache.cassandra.db.compaction.CompactionManager$
	at java.util.concurrent.FutureTask$Sync.innerRun(
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
	at java.util.concurrent.ThreadPoolExecutor$

kind regards,

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message