[
https://issues.apache.org/jira/browse/CASSANDRA-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Kjellman resolved CASSANDRA-5116.
-----------------------------------------
Resolution: Not A Problem
Assignee: Michael Kjellman (was: Yuki Morishita)
appears randomly -Summary.db files for random sstables across all the nodes in
the cluster got a umask of 600 instead of 644.
all sstables are owned by cassandra:cassandra so i'm not sure why 600 on the
-Summary.db files would lead to an issue where files are not compacted.
After talking to [~yukim] for a while on this he said that the *-Summary.db
files are created during the upgrade to 1.2.0
I'm also wondering if this is a manifestation of #5102
> 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
