[
https://issues.apache.org/jira/browse/CASSANDRA-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13544249#comment-13544249
]
Michael Kjellman commented on CASSANDRA-5116:
---------------------------------------------
when attempting to do a forceUserDefinedCompaction on the sstable's in question
this is logged:
{code}
INFO 12:50:39,748 Will not compact ks/ks-evidence_index-hf-70: it is not an
active sstable
INFO 12:50:39,749 No file to compact for user defined compaction
{code}
which according to the source looks like lookupSSTable() returned null.
which begs the question then, why are these sstables still getting streamed
then?
> 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
>
> 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
