[
https://issues.apache.org/jira/browse/CASSANDRA-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464301#comment-13464301
]
Tyler Patterson commented on CASSANDRA-4698:
--------------------------------------------
Per Pavel's request I ran the test again. Everything checked out, here are the
steps followed:
1: get that data onto both nodes in a 1.1.1 cluster
2: upgrade and start node2 on 1.1.5+patch
3: stop both nodes
4: start node1 (1.1.1) and verify that timestamps are fixed (zero last 3
digits)
5: stop node1
6: start node2 (1.1.5+patch), verify that timestamps are fixed (3 zeros)
7: nodetool resetlocalschema on node2
8: Verify that the troublesome keyspace is *not* present on node2
9: stop node2
10: start node1
11: start node2
12: verify that the troublesome keyspace appears on node2 and timestamps are
fixed (3 zeros)
> 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: CASSANDRA-4698.patch, 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
