Re: [PR] CASSSIDECAR-486: Prefer exact-range CDC checkpoint on load to avoid restart rewind [cassandra-sidecar]

["bbotella (via GitHub)" <gi...@apache.org>]

bbotella commented on PR #372:
URL: https://github.com/apache/cassandra-sidecar/pull/372#issuecomment-5662531351

   Mmmm, I have a doubt here. Let's say:
   
   1. Job runs on range R1=(s1,e1) for a while, checkpoint row1 advances normally.
   2. Topology change reassigns it to R2=(s2,e2) (overlaps R1, different boundaries). First write for R2 correctly falls back to the full overlap set (no exact match yet), inherits row1's progress via min-merge, and starts writing row2. Row2 keeps advancing past where row1 ever got.
   3. Another topology change reassigns the job back to R1's exact boundaries.
   4. On load, exactRangeMatch finds row1 — an exact boundary match — and per the fix's logic, that wins outright, discarding row2 entirely, even though row2 is overlapping and strictly newer/further along than row1.
   
   I know this event is rarer than the one this patch is addressing, but still possible, right? 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org