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

Jonathan Ellis commented on CASSANDRA-4698:
-------------------------------------------

ISTM that only fixing remote timestamps is the wrong solution in general -- it 
fixes this particular scenario, but re-introduces "unmodifiable" keyspaces, 
since the [local] timestamp is now permanently left unnaturally high.

I think that we need to fix it at a higher level than serialization: once the 
rows [from different sstables] have all been deserialized and merged, THEN fix 
the timestamp.  Then we won't have the problem of an adjusted tombstone 
clobbering a value that it didn't, pre-adjustment.
                
> 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 cass@50.57.69.32:/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