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

schedule: fix a thread-safe bug and improve code (#1719) #1734

Merged
merged 15 commits into from
Sep 11, 2019

Conversation

Luffbee
Copy link
Contributor

@Luffbee Luffbee commented Sep 6, 2019

What problem does this PR solve?

cherry-pick #1719

@Luffbee Luffbee requested review from nolouch and rleungx and removed request for nolouch September 7, 2019 04:09
@nolouch
Copy link
Contributor

nolouch commented Sep 9, 2019

/run-all-tests tidb=release-3.0 tikv=release-3.0 tidb-test=release-3.0

Copy link
Contributor

@nolouch nolouch left a comment

Choose a reason for hiding this comment

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

lgtm

@nolouch nolouch added the status/LGT1 Indicates that a PR has LGTM 1. label Sep 9, 2019
server/schedule/operator_controller.go Outdated Show resolved Hide resolved
server/schedule/operator_controller.go Outdated Show resolved Hide resolved
Copy link
Member

@rleungx rleungx left a comment

Choose a reason for hiding this comment

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

After thinking about it, I think we don't need to update these two metrics. Because the people who upgrade PD to the next version maybe not upgrade tidb-ansible.

@Luffbee
Copy link
Contributor Author

Luffbee commented Sep 10, 2019

After thinking about it, I think we don't need to update these two metrics. Because the people who upgrade PD to the next version maybe not upgrade tidb-ansible.

Changed them back.

@nolouch nolouch added needs-cherry-pick-release-3.1 The PR needs to cherry pick to release-3.1 branch. status/can-merge Indicates a PR has been approved by a committer. labels Sep 11, 2019
@sre-bot
Copy link
Contributor

sre-bot commented Sep 11, 2019

Your auto merge job has been accepted, waiting for 1748

@sre-bot
Copy link
Contributor

sre-bot commented Sep 11, 2019

/run-all-tests

@sre-bot
Copy link
Contributor

sre-bot commented Sep 11, 2019

cherry pick to release-3.1 in PR #1751

@Luffbee Luffbee deleted the cherry-pick-1719-3.0 branch October 15, 2019 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-cherry-pick-release-3.1 The PR needs to cherry pick to release-3.1 branch. status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants