[
https://issues.apache.org/jira/browse/CASSANDRA-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13544527#comment-13544527
]
Michael Kjellman commented on CASSANDRA-5116:
---------------------------------------------
more on this:
1) did a cleanup on the node...the sstables that weren't upgraded were left
alone by the cleanup operation
2) the log files show cassandra opening the sstable
3) i set row and key caches to 0, cleared everything in saved_caches and
physically restarted the node to clear the kernel cache, i've now seen at least
one of the sstables getting upgraded in my 4th attempt on this particular node
to upgrade sstables.
developing... :)
> 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
