-
Notifications
You must be signed in to change notification settings - Fork 499
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
Stability cases: stop kubelet and etcd #665
Conversation
* pv data safe
@@ -173,7 +173,7 @@ func (oa *operatorActions) CheckFailoverPending(info *TidbClusterConfig, node st | |||
if _, exist := affectedPods[failureStore.PodName]; exist { | |||
err := fmt.Errorf("cluster: [%s] the tikv store[%s] should be mark failure after %s", info.FullName(), failureStore.PodName, deadline.Format(time.RFC3339)) | |||
glog.Errorf(err.Error()) | |||
return false, err | |||
return false, nil |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There may have been a failover before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be a comment in the code?
@@ -950,7 +1020,8 @@ func (oa *operatorActions) CheckUpgrade(ctx context.Context, info *TidbClusterCo | |||
} | |||
glog.V(4).Infof("index:%d,schedulers:%v,error:%v", i, schedulers, err) | |||
if len(schedulers) > 1 { | |||
return true, fmt.Errorf("there are too many evict leader schedulers: %v", schedulers) | |||
glog.Errorf("there are too many evict leader schedulers: %v", schedulers) | |||
return false, nil |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There may be two schedulers at the same time
/run-e2e-tests |
/run-e2e-tests |
/run-e2e-tests |
/run-e2e-tests |
1 similar comment
/run-e2e-tests |
(cherry picked from commit d9851bf)
What problem does this PR solve?
What is changed and how does it work?
Check List
Tests
Code changes
Side effects
Related changes
Does this PR introduce a user-facing change?: