[jira] [Comment Edited] (CASSANDRA-5116) upgradesstables does not upgrade all sstables on a node

["Michael Kjellman (JIRA)" <ji...@apache.org>]

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

Michael Kjellman edited comment on CASSANDRA-5116 at 1/7/13 11:50 PM:
----------------------------------------------------------------------

appears that once again i was wrong. this doesn't seem to be affected by permissions after all

with org.apache.cassandra.db.DataTracker set to DEBUG, it looks like somehow the sstables are not getting added to the list of active sstables by DataTracker for that column family

also, i run C* with two datanodes, one for each spindle. It appears that the non-upgraded sstables are always all in one data directory while the other data directory has no non-upgraded sstables.

going to resolve this again, i'm pretty sure there is a bug here somewhere. Maybe these are all sstables that should be deleted but we fail to remove for some reason?

maybe someone else (hopefully not) will run into this and can reopen and debug again.
                
      was (Author: mkjellman):
    appears that once again i was wrong. this doesn't seem to be affected by permissions after all

with org.apache.cassandra.db.DataTracker set to DEBUG, it looks like somehow the sstables are not getting added to the list of active sstables by DataTracker for that column family

                  
> 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: Michael Kjellman
>
> 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