iirc I reviewed it and mentioned this is not a correctness issue since we would simply re-prepare. I can't recall why we needed to evict, but I think this was for correctness reasons.
Would you mind to elaborate why simply letting it to get re-prepared is harmful behavior? Or am I missing something and this has larger implications? To be clear, I am not opposed to this patch, just want to understand implications better. On Sun, Dec 14, 2025, at 9:03 PM, Jaydeep Chovatia wrote: > Hi > > I had reported this bug (CASSANDRA-17401 > <https://issues.apache.org/jira/browse/CASSANDRA-17401>) in 2022 along with > the fix (PR#3059 <https://github.com/apache/cassandra/pull/3059>) and a > reproducible (PR#3058 <https://github.com/apache/cassandra/pull/3058>). I > already applied this fix internally, and it has been working fine for many > years. Now we can see one of the Cassandra users has been facing the exact > same problem. I have told them to go with the private fix for now. > Paulo and Alex had reviewed it partially, could you (or someone) please > complete the review so I can land to the official repo. > > Jaydeep
