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

LegacySplitCloneWorker is no longer used in any code paths #8867

Merged
merged 2 commits into from
Sep 22, 2021

Conversation

mattlord
Copy link
Contributor

Signed-off-by: Matt Lord [email protected]

Description

Keeping things tidy...

Related Issue(s)

#4456

Checklist

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

Keeping things tidy...

Signed-off-by: Matt Lord <[email protected]>
@rafael
Copy link
Member

rafael commented Sep 22, 2021

Wow - end of an era! Excited to see this go. For completeness, we should not allow LegacySlitClone as an option from here.

Also, we should delete the resharding workflow entirely. But that could be a different PR.

@mattlord
Copy link
Contributor Author

Wow - end of an era! Excited to see this go. For completeness, we should not allow LegacySlitClone as an option from here.

I tried to remove the remaining references in bfcfcb9

Let me know if you had something else in mind.

Also, we should delete the resharding workflow entirely. But that could be a different PR.

I'm actually not sure what you mean here and how it's related.

Thanks!

@mattlord
Copy link
Contributor Author

mattlord commented Sep 22, 2021

Also, we should delete the resharding workflow entirely. But that could be a different PR.

@rafael Were you saying that we should remove the non-legacy SplitClone code too now that you should be using MoveTables instead in 6.0+? If so, then I think we probably should but can be done in a separate PR.

@rafael
Copy link
Member

rafael commented Sep 22, 2021

Wow - end of an era! Excited to see this go. For completeness, we should not allow LegacySlitClone as an option from here.

I tried to remove the remaining references in bfcfcb9

Let me know if you had something else in mind.

Perfect, this what I had in mind.

Also, we should delete the resharding workflow entirely. But that could be a different PR.

I'm actually not sure what you mean here and how it's related.

What I meant is that go/vt/workflow/resharding is all related to legacy code paths (pre vreplication and the new resharding methods). I'm thinking of this sequence:

  • After removing LegacySplitClone, SplitClone could be removed as well.
  • Then we can remove go/vt/workflow/resharding , reshardingworkflowgen and the related UI code in vtctld.

That could be in subsequent PR's, it would take this cleanup even further 🎉

Thanks!

Copy link
Member

@rafael rafael left a comment

Choose a reason for hiding this comment

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

LGTM

@rafael rafael merged commit b79db56 into vitessio:main Sep 22, 2021
@mattlord mattlord deleted the RemoveDeadLegacySplitCloneWorker branch September 27, 2021 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants