Skip to content

placement: cherry-pick #30859#31179

Closed
xhebox wants to merge 1 commit into
pingcap:release-5.3from
xhebox:placement_2
Closed

placement: cherry-pick #30859#31179
xhebox wants to merge 1 commit into
pingcap:release-5.3from
xhebox:placement_2

Conversation

@xhebox
Copy link
Copy Markdown
Contributor

@xhebox xhebox commented Dec 30, 2021

What problem does this PR solve?

Issue Number: close #xxx

Problem Summary: As title, refer #30859 #30858

What is changed and how it works?

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No code

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

Fix schedule error for placement rules using sugar syntax, i.e. `PRIMARY_REGION`

@ti-chi-bot
Copy link
Copy Markdown
Member

ti-chi-bot commented Dec 30, 2021

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • lcwangchao

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Details

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@xhebox xhebox requested a review from a team as a code owner December 30, 2021 09:07
@ti-chi-bot
Copy link
Copy Markdown
Member

@xhebox: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ti-chi-bot ti-chi-bot added do-not-merge/cherry-pick-not-approved release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Dec 30, 2021
@xhebox xhebox removed the request for review from a team December 30, 2021 09:07
Signed-off-by: xhe <xw897002528@gmail.com>
@xhebox xhebox force-pushed the placement_2 branch 2 times, most recently from cb8865b to 223611b Compare December 30, 2021 09:13
@ti-chi-bot ti-chi-bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Dec 30, 2021
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Dec 30, 2021
@xhebox xhebox closed this Jan 11, 2022
@xhebox xhebox deleted the placement_2 branch January 11, 2022 05:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/cherry-pick-not-approved release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. status/LGT1 Indicates that a PR has LGTM 1.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants