+1 on rejection-by-default, for several reasons: 1) Jordan’s point on the fact that recovery from this kind of data misplacement is very difficult. 2) Without any sort of warning or error in existing Cassandra installations, how many operators/users would actually know that they have been hit by this particular issue in the past? My guess is that the folks who have actually identified instances of this kind of data loss are ones who have a significant amount of experience running Cassandra and a team that has the ability to track down these kinds of issues, where most users may have never even known this was happening.
If we only warn/log, most folks will likely either not even see the issue (we log a lot) or not know what to do when it happens. Doug > On Sep 12, 2024, at 2:19 PM, Brandon Williams <dri...@gmail.com> wrote: > > On Thu, Sep 12, 2024 at 1:13 PM Caleb Rackliffe > <calebrackli...@gmail.com> wrote: >> >> I think I can count at least 4 people on this thread who literally have lost >> sleep over this. > > Probably good examples of not being the majority though, heh. > > If we are counting on users to read NEWS.txt, can we not count on them > to enable rejection if this is important to them? > > Kind Regards, > Brandon
