Incremental remote bootstraps #1217
Labels
area/docdb
YugabyteDB core features
kind/enhancement
This is an enhancement of an existing feature
priority/medium
Medium priority issue
Projects
Jira Link: DB-2203
Currently, if a tablet decides to remote bootstrap a peer who is lagging behind, the peer deletes all the data and fetches everything from the leader.
This may not be the best decision if there is a lot of data in the tablet. And, it seems wasteful to delete all the data corresponding to the time until when the peer was caught up.
We should consider supporting Incremental Remote Bootstraps where the lagging-behind peer can fetch just the sst files and logs corresponding to the delta that the peer has missed.
The text was updated successfully, but these errors were encountered: