For what it's worth, I don't think this impacts 3.0 without adding some other code change (the reporter of the bug on 3.0 had added custom metrics that exposed a concurrency issue).
We're looking at it on 3.11. I think 13038 made it far more likely to occur, but I think it could have happened pre-13038 as well (would take some serious luck with your deletion time distribution though - the rounding in 13038 does make it more likely, but the race was already there). -- Jeff Jirsa > On Aug 28, 2017, at 8:24 PM, Jay Zhuang <jay.zhu...@yahoo.com.INVALID> wrote: > > We're using 3.0.12+ for a few months and haven't seen the issue like > that. Do we know what could trigger the problem? Or is 3.0.x really > impacted? > > Thanks, > Jay > >> On 8/28/17 6:02 AM, Hannu Kröger wrote: >> Hello, >> >> Current latest Cassandra version (3.11.0, possibly also 3.0.12+) has a race >> condition that causes Cassandra to create broken sstables (stats file in >> sstables to be precise). >> >> Bug described here: >> https://issues.apache.org/jira/browse/CASSANDRA-13752 >> >> This change might be causing it (but not sure): >> https://issues.apache.org/jira/browse/CASSANDRA-13038 >> >> Other related issues: >> https://issues.apache.org/jira/browse/CASSANDRA-13718 >> https://issues.apache.org/jira/browse/CASSANDRA-13756 >> >> I would not recommend using 3.11.0 nor upgrading to 3.0.12 or higher before >> this is fixed. >> >> Cheers, >> Hannu >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
