[
https://issues.apache.org/jira/browse/CASSANDRA-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804342#action_12804342
]
Jonathan Ellis commented on CASSANDRA-735:
------------------------------------------
Is this reproducible in trunk or a heisenbug? Did you try 0.5?
> Bootstrapping with replication factor of 1
> ------------------------------------------
>
> Key: CASSANDRA-735
> URL: https://issues.apache.org/jira/browse/CASSANDRA-735
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: Chris Goffinet
> Fix For: 0.6
>
>
> I was testing a 2 node cluster w/ replication factor of 1. I added another
> node to cluster. (RackAwareStrategy)
> New Node: 10.2.128.43
> Node Moving Data: 10.2.128.38
> .38 starts anticompacting and begins streaming data over. On node .43 I see
> stream added messages in log file, and it looks like all streams are
> finished.
> Node .38:
> INFO [COMPACTION-POOL:1] 2010-01-24 15:33:37,954 CompactionManager.java
> (line 364) AntiCompacting []
> INFO [STREAM-STAGE:1] 2010-01-24 15:33:37,961 Streaming.java (line 136)
> Waiting for transfer to /10.2.128.43 to complete
> Node .43 is doing nothing at this point besides removing some SSTables that
> need to be deleted and few compactions. I noticed this that seemed little
> strange:
> INFO [AE-SERVICE-STAGE:1] 2010-01-24 15:33:40,792 AntiEntropyService.java
> (line 233) Sending AEService tree for (Digg,Users) to: [/10.2.128.38]
> I saw 2 of these occur after streaming added. It seems node .38 is waiting on
> .43 to acknowledge streaming is finished but it never occurs, so the node
> never completes bootstrap.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
