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

Sylvain Lebresne commented on CASSANDRA-3967:
---------------------------------------------

There is a small bug in that after renaming we try to load the old (before 
renaming) descriptor. Added commit to 
https://github.com/pcmanus/cassandra/commits/3967-2 to fix that. With that, and 
while I don't have a windows and can't vouch that it fixes tests there, since 
that is anyway a more reasonable way to load new sstables, +1.
                
> Test fixes for Windows
> ----------------------
>
>                 Key: CASSANDRA-3967
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3967
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 1.1.0
>
>         Attachments: 3967.txt
>
>
> - SchemaLoader initializes CommitLog, creating empty segments; CleanupHelper 
> then errors out trying to delete them (because they are still open)
> - CFS.clearUnsafe resets the sstable generation but does not remove the 
> sstables involved, so Windows will error out trying to rename over the 
> existing ones

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to