Hi Todd,
While looking at KUDU-1408, which addresses catch-up-game between bootstrapping a new replica and log retention on existing replicas, few basic Qs popping up in mind: Looking at description of LogAnchor class, what’s the purpose of log anchor generally. Also, is this any different from rejoining a stale replica to the cluster ? (stale could mean going as far back as starting a new replica ?) Instead of sending anchor logs via heartbeats(as you seem to be suggesting in the bug), could we not rely on the follower to suggest the leader where he wants to replay the logs from ? In other words, the ’tablet copy' begins with leader asking the follower what was his(or her ) last known index. I am confident I am missing several pieces here. Thanks, Dinesh.
