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 updates needed for placement rules #31487

Closed
Tracked by #18030
xhebox opened this issue Jan 10, 2022 · 1 comment · Fixed by pingcap/docs#7400
Closed
Tracked by #18030

Documentation updates needed for placement rules #31487

xhebox opened this issue Jan 10, 2022 · 1 comment · Fixed by pingcap/docs#7400
Assignees
Labels
type/enhancement The issue or PR belongs to an enhancement.

Comments

@xhebox
Copy link
Contributor

xhebox commented Jan 10, 2022

Enhancement

Sub task of #18030

  1. The main page of the user doc, did not talk about show placement. So some users does not know about show placement at all. Three people has asked this question.
  2. We did not point out clearly that ALTER PLACEMENT POLICY is full override for the existing policies in the user doc. Two people has asked this question and try ALTER PLACEMENT POLICY p FOLLOWERS=2 to adjust the replication numbers. I think it can be added as an counter-example.
  3. PENDING scheduling state for show placement, for both rfc and user docs.
  4. remove direct placement for both rfc and user docs.
@xhebox xhebox added the type/enhancement The issue or PR belongs to an enhancement. label Jan 10, 2022
@xhebox xhebox self-assigned this Jan 10, 2022
@xhebox
Copy link
Contributor Author

xhebox commented Jan 10, 2022

I would like to change the user document, but our assignment is not clear @morgo . Let us make it clear.

But whatever I could the chinese changes to user documents, since translators did not understand placement policies well, based on their previous translation of the user documents.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant