You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New shards are created with IsPrimaryServing=true. So VDiffs for forward workflows work since the picker does pick tablets from the new shards.
However when we switch primary traffic we set IsPrimaryServing=false for the shards we are switching away from. This means that the picker for reverse workflows does not find any tablets so source the target streams from.
Note that the reverse workflow itself is still running properly.
Found while debugging failed vdiffs for the reverse workflows in #14327
Reproduction Steps
Run local example upto and including ./305_switch_writes.sh.
Start a vdiff for the reverse workflow with vtctlclient VDiff -- --tablet_types=replica customer.cust2cust_reverse create
Check that it doesn't progress using vtctlclient VDiff customer.cust2cust show last
Binary Version
vttablet version Version: 19.0.0-SNAPSHOT (Git revision eddb7da44636994d1064906ca20d06543e6044a0 branch 'main') built on Tue Oct 31 11:48:06 CET 2023 by [email protected] using go1.21.0 darwin/arm64
Overview of the Issue
VDiffs that are created for reverse workflows do not start because they cannot find any tablets to stream from on the original source:
IsPrimaryServing=true
. So VDiffs for forward workflows work since the picker does pick tablets from the new shards.IsPrimaryServing=false
for the shards we are switching away from. This means that the picker for reverse workflows does not find any tablets so source the target streams from.Note that the reverse workflow itself is still running properly.
Found while debugging failed vdiffs for the reverse workflows in #14327
Reproduction Steps
./305_switch_writes.sh
.vtctlclient VDiff -- --tablet_types=replica customer.cust2cust_reverse create
vtctlclient VDiff customer.cust2cust show last
Binary Version
Operating System and Environment details
Log Fragments
The text was updated successfully, but these errors were encountered: