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

Documentation link problem http://vitess.io/user-guide/horizontal-sharding-workflow/ #3238

Closed
sjmudd opened this issue Sep 23, 2017 · 2 comments · Fixed by #3240
Closed

Documentation link problem http://vitess.io/user-guide/horizontal-sharding-workflow/ #3238

sjmudd opened this issue Sep 23, 2017 · 2 comments · Fixed by #3240

Comments

@sjmudd
Copy link
Contributor

sjmudd commented Sep 23, 2017

I notice some links here http://vitess.io/user-guide/horizontal-sharding-workflow/ at the top of the page which give a 404. This probably needs fixing.

michael-berlin added a commit to michael-berlin/vitess that referenced this issue Sep 23, 2017
Affected page: http://vitess.io/user-guide/horizontal-sharding-workflow/

This broke when I changed the URL format in vitessio#3183.

I fixed it by removing the file name from the link. Note that the links should not have included the file name to begin with.

Fixes vitessio#3238.
@michael-berlin
Copy link
Contributor

Thanks for the report. I've fixed this now.

In general, note that the "workflow" in "Horizontal Resharding Workflow" stands for our workflow automation. You find this automation in the vtctld UI.

Therefore we have two tutorials, one for an automated resharding and one for a manual resharding:

automated: http://vitess.io/user-guide/horizontal-sharding-workflow/
manual: http://vitess.io/user-guide/horizontal-sharding/

As far as I understand, you're currently not using the automation and instead run SplitClone manually? In any case, the information on both pages should be correct.

@sjmudd
Copy link
Contributor Author

sjmudd commented Sep 23, 2017

Thanks for the clarification.

Yes, right now I'm doing this manually as I'm trying to reshard from a non-vitess source (using only RDONLY vttablets connected to a couple of slaves). Understanding the manual workflow is good but having something that automates this when the system is up and running normally is obviously very attractive. I'll re-read both sections again.

frouioui pushed a commit to planetscale/vitess that referenced this issue Mar 26, 2024
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 a pull request may close this issue.

2 participants