cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Kjellman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5116) upgradesstables does not upgrade all sstables on a node
Date Sat, 05 Jan 2013 10:12:14 GMT

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

Michael Kjellman commented on CASSANDRA-5116:
---------------------------------------------

caches and the system cache had no effect on this so not sure if the cleanup was the reason
more hf files were compacted during the upgrade. I did notice that after i restarted the node,
caches etc there were 4 out of 20-30+ pending sstables that did get upgraded. so it's not
like certain sstables refuse to get upgraded.
                
> upgradesstables does not upgrade all sstables on a node
> -------------------------------------------------------
>
>                 Key: CASSANDRA-5116
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5116
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>         Environment: Ubuntu 12.04
>            Reporter: Michael Kjellman
>            Assignee: Yuki Morishita
>
> upgradesstables appears to be skipping sstables randomly.
> finding a sstable with an mtime < the upgrade time and grepping through the logs for
a corresponding compaction log line, i find nothing. I have reproduced this on all of my nodes
across the cluster.
> is performAllSSTableOperation somehow skipping sstables?

--
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

Mime
View raw message