Hello everyone, We ran into some nasty bug while upgrading to Cassandra 3.11: https://issues.apache.org/jira/browse/CASSANDRA-13752
Basically there is possible race condition in tombstone histogram serialization. If someone modifies tombstone histogram after size is serialized but before entries are serialized then you will end up in the situation where stats files tells that you have X entries in the histogram but after that you actually have X+N (N=1 seen in wild) entries written in the file. Cassandra cannot deserialize that when it next time reads the file (after a restart at least). I have a fix for it: https://github.com/hkroger/cassandra/tree/cassandra-3.11-13752 Writing a test for it is a bit hard. Also testing manually that it actually fixes it is hard so… How can we push this forward? It’s sort of critical for us and I would like some more experienced C* dev to give fatherly or motherly advice :) BR, Hannu Kröger
