For 7.0, we have the following lines:
Normally, when raising a backfill, XDCR will go figure out the throughSeqno and compile a backfill task for each VB going from 0 to whatever the throughSeqno is.
When the pipeline is stopped and not running, it will retrieve 0. Instead, it should follow the other path of
and capture checkpoint number, in case the pipeline is stopped.
For 7.0, it's not a huge issue because the first call only happens during pipeline runtime. (Can consider this for backport just in case).
However, this is a hole that should be fixed in preparation for 7.1 and the
|For Gerrit Dashboard: MB-47779|
|158952,2||MB-47779 - backfill req handler may not get correct throughSeqnos if pipeline is paused||cheshire-cat||goxdcr||Status: MERGED||+2||+1|