stable scheduling: fix bug in reporting assigned nodes of tidb members #531
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cofyc
commented
May 28, 2019
| @@ -389,6 +389,7 @@ func (tmm *tidbMemberManager) syncTidbClusterStatus(tc *v1alpha1.TidbCluster, se | |||
| oldTidbMember, exist := tc.Status.TiDB.Members[name] | |||
| if exist { | |||
| newTidbMember.LastTransitionTime = oldTidbMember.LastTransitionTime | |||
| newTidbMember.NodeName = oldTidbMember.NodeName | |||
There was a problem hiding this comment.
copy the old value because we should not clear it in any case (e.g. new pod is in pending status)
|
/run-e2e-tests |
weekface
approved these changes
May 29, 2019
aylei
approved these changes
May 29, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
fix bug in reporting assigned nodes of tidb members
What is changed and how it works?
Check List
Code changes
Does this PR introduce a user-facing change?: