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

Benedict commented on CASSANDRA-6974:
-------------------------------------

[~enigmacurry] I get different errors when I run this dtest. Initially, I get:

{noformat}
Streaming session ID: 25dea2f0-be47-11e3-8aa4-f765879d36e5
Exception in thread "STREAM-OUT-/127.0.0.1" java.lang.NullPointerException
        at 
org.apache.cassandra.streaming.ConnectionHandler$MessageHandler.signalCloseDone(ConnectionHandler.java:249)
        at 
org.apache.cassandra.streaming.ConnectionHandler$OutgoingMessageHandler.run(ConnectionHandler.java:375)
        at java.lang.Thread.run(Thread.java:744)
{noformat}

then, after fixing, I get

{noformat}
Exception in thread "STREAM-OUT-/127.0.0.1" java.lang.NullPointerException
        at 
org.apache.cassandra.streaming.StreamManager$StreamRateLimiter.<init>(StreamManager.java:79)
        at 
org.apache.cassandra.streaming.StreamManager.getRateLimiter(StreamManager.java:61)
        at 
org.apache.cassandra.streaming.StreamWriter.<init>(StreamWriter.java:60)
        at 
org.apache.cassandra.streaming.compress.CompressedStreamWriter.<init>(CompressedStreamWriter.java:47)
        at 
org.apache.cassandra.streaming.messages.OutgoingFileMessage$1.serialize(OutgoingFileMessage.java:51)
        at 
org.apache.cassandra.streaming.messages.OutgoingFileMessage$1.serialize(OutgoingFileMessage.java:40)
        at 
org.apache.cassandra.streaming.messages.StreamMessage.serialize(StreamMessage.java:45)
        at 
org.apache.cassandra.streaming.ConnectionHandler$OutgoingMessageHandler.sendMessage(ConnectionHandler.java:384)
        at 
org.apache.cassandra.streaming.ConnectionHandler$OutgoingMessageHandler.run(ConnectionHandler.java:355)
        at java.lang.Thread.run(Thread.java:744)
{noformat}

Is it possible the config for the test is specific to your setup? Looks like 
it's failing to find a localDc.

> Replaying archived commitlogs isn't working
> -------------------------------------------
>
>                 Key: CASSANDRA-6974
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6974
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Ryan McGuire
>            Assignee: Benedict
>             Fix For: 2.1 beta2
>
>         Attachments: 2.0.system.log, 2.1.system.log
>
>
> I have a test for restoring archived commitlogs, which is not working in 2.1 
> HEAD.  My commitlogs consist of 30,000 inserts, but system.log indicates 
> there were only 2 mutations replayed:
> {code}
> INFO  [main] 2014-04-02 11:49:54,173 CommitLog.java:115 - Log replay 
> complete, 2 replayed mutations
> {code}
> There are several warnings in the logs about bad headers and invalid CRCs: 
> {code}
> WARN  [main] 2014-04-02 11:49:54,156 CommitLogReplayer.java:138 - Encountered 
> bad header at position 0 of commit log /tmp/dtest
> -mZIlPE/test/node1/commitlogs/CommitLog-4-1396453793570.log, with invalid 
> CRC. The end of segment marker should be zero.
> {code}
> compare that to the same test run on 2.0, where it replayed many more 
> mutations:
> {code}
>  INFO [main] 2014-04-02 11:49:04,673 CommitLog.java (line 132) Log replay 
> complete, 35960 replayed mutations
> {code}
> I'll attach the system logs for reference.
> [Here is the dtest to reproduce 
> this|https://github.com/riptano/cassandra-dtest/blob/master/snapshot_test.py#L75]
>  - (This currently relies on the fix for snapshots available in 
> CASSANDRA-6965.)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to