Skip to content

Vtctl Workflow cmd: don't expect all shards to have workflow streams#6576

Merged
sougou merged 1 commit intovitessio:masterfrom
planetscale:rn-vexec-fix-list-reshardedks
Aug 17, 2020
Merged

Vtctl Workflow cmd: don't expect all shards to have workflow streams#6576
sougou merged 1 commit intovitessio:masterfrom
planetscale:rn-vexec-fix-list-reshardedks

Conversation

@rohit-nayak-ps
Copy link
Copy Markdown
Member

Signed-off-by: Rohit Nayak rohit@planetscale.com

Signed-off-by: Rohit Nayak <rohit@planetscale.com>
Copy link
Copy Markdown
Collaborator

@deepthi deepthi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we document the original issue in this PR?
Looks good otherwise.

@sougou sougou merged commit 75a829c into vitessio:master Aug 17, 2020
@rohit-nayak-ps
Copy link
Copy Markdown
Member Author

This PR fixes a bug in VExec. Currently it expects the same workflow to be present in all shards in a keyspace, which is of course not the case in resharding until the source shards have been dropped. During resharding, only the target shards will have the forward workflow and the source shards will have the reverse workflow (once writes have been switched to the target).

Signed-off-by: Rohit Nayak rohit@planetscale.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants