Skip to:
Currently we have our DCP client for DCP based resync set to fail on rollback. -> https://github.com/couchbase/sync_gateway/blob/246fde2151448dbbaa2f7c4a19d133c16abd2b29/db/background_mgr_resync_dcp.go#L333C11-L333C11
We should have either handling like our attachment compaction rollback handling or just allow ourselves to rollback to whatever KV requires and reprocess these documents again, removing the need to fail on rollback.
Build sync_gateway-3.2.0-350 contains sync_gateway commit ed3408d with commit message:[3.1.2 backport] turn off failOnRollback for resync #6469
Build sync_gateway-3.2.0-348 contains sync_gateway commit ed3408d with commit message:[3.1.2 backport] turn off failOnRollback for resync #6469
Build sync_gateway-3.2.0-346 contains sync_gateway commit ed3408d with commit message:[3.1.2 backport] turn off failOnRollback for resync #6469
Build sync_gateway-3.2.0-344 contains sync_gateway commit ed3408d with commit message:[3.1.2 backport] turn off failOnRollback for resync #6469
Build sync_gateway-3.2.0-342 contains sync_gateway commit ed3408d with commit message:[3.1.2 backport] turn off failOnRollback for resync #6469
Currently we have our DCP client for DCP based resync set to fail on rollback. -> https://github.com/couchbase/sync_gateway/blob/246fde2151448dbbaa2f7c4a19d133c16abd2b29/db/background_mgr_resync_dcp.go#L333C11-L333C11
We should have either handling like our attachment compaction rollback handling or just allow ourselves to rollback to whatever KV requires and reprocess these documents again, removing the need to fail on rollback.