Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V2 Workflow Start: wait for streams to start and report errors if any while starting a workflow #7248

Merged

Conversation

rohit-nayak-ps
Copy link
Contributor

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

Description

When a MoveTables or Reshard Start is invoked:

  • polls streams on target
  • if the Message column contains an Error report it
  • if streams don't start before the timeout specified stop polling

Note that the workflow itself is not aborted. This just tells the user that there are possible issues and they need to fix it and then possibly restart the streams using the Workflow command or VExec/VReplicationExec if any custom repair is needed.

Related Issue(s)

#7071

Checklist

  • Should this PR be backported?
  • Tests were added or are not required
  • Documentation was added or is not required

Impacted Areas in Vitess

Components that this PR will affect:

  • Query Serving
  • VReplication
  • Cluster Management
  • Build

… start within timeout, improve Show output

Signed-off-by: Rohit Nayak <rohit@planetscale.com>
Signed-off-by: Rohit Nayak <rohit@planetscale.com>
@rohit-nayak-ps rohit-nayak-ps marked this pull request as ready for review January 5, 2021 00:48
@rohit-nayak-ps rohit-nayak-ps removed the request for review from doeg January 5, 2021 00:49
@rohit-nayak-ps rohit-nayak-ps merged commit 4aac378 into vitessio:master Jan 5, 2021
@rohit-nayak-ps rohit-nayak-ps deleted the rn-wait-for-workflow-start branch January 5, 2021 09:21
@askdba askdba added this to the v9.0 milestone Jan 6, 2021
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.

3 participants