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

Tyler Patterson commented on CASSANDRA-4698:
--------------------------------------------

{quote}It sounds like this reproduces on a single node? No schema disagreement 
should be necessary/possible.{quote}
yes, this happened on a single node.

{quote} Can you try this test out and let me know if the keyspace reappears? 
...{quote}
Yes. I did those steps on one of the columnfamilies in the keyspace and the 
data did indeed come back.
                
> Keyspace disappears when upgrading node from cassandra-1.1.1 to 
> cassandra-1.1.5
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4698
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4698
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.5
>         Environment: ubuntu. JNA not installed.
>            Reporter: Tyler Patterson
>            Assignee: Pavel Yaskevich
>             Fix For: 1.1.6
>
>         Attachments: start_1.1.1_system.log, start_1.1.5_system.log
>
>
> Here is how I got the problem to happen:
> 1. Get this zipped data directory (about 33Mb):
>   scp [email protected]:/home/cass/cassandra.zip ./ (password cass)
> 2. Unzip it in /var/lib/
> 3. clone the cassandra git repo
> 4. git checkout cassandra-1.1.1; ant jar;
> 5. bin/cassandra 
> 6. Run cqlsh -3, then DESC COLUMNFAMILIES; Note the presence of Keyspace 
> performance_tests
> 7. pkill -f cassandra; git checkout cassandra-1.1.5; ant realclean; ant jar;
> 8. bin/cassandra
> 9. Run cqlsh -3, then DESC COLUMNFAMILIES; Note that there is no 
> performance_tests keyspace

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to