-
Notifications
You must be signed in to change notification settings - Fork 102
Conversation
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.
Rest LGTM
pkg/pdutil/pd.go
Outdated
if failure == nil { | ||
break | ||
} | ||
} | ||
if failure != nil { | ||
return nil, errors.Annotatef(failure, "pd address (%s) not available, please check network", pdAddrs) | ||
} | ||
version, err := semver.NewVersion(string(versionBytes)) | ||
if err != nil { | ||
return nil, errors.Annotatef(err, "transform pd version failed", string(versionBytes)) |
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.
Could you choose an error in pkg/errors?
8ac48a5
to
668a2c9
Compare
668a2c9
to
7cf0c64
Compare
/rebuild |
e63d085
to
99692eb
Compare
b3fdef9
to
64d6d4c
Compare
/run-integration-test |
f7552b6
to
002f54c
Compare
pkg/pdutil/pd.go
Outdated
expectPDCfg = map[string]interface{}{ | ||
"max-merge-region-keys": 0, | ||
"max-merge-region-size": 0, | ||
// TODO remove this schedule-limits, see https://github.com/pingcap/br/pull/555#discussion_r509855972 |
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.
as the rationale keeping the two -limit
s in #555 was
I think we could leave a TODO here and try to merge this firstly... I'm afraid that if any error occurs during editing, we cannot merge this in the current unstable CI environment...
do we still need to keep them here?
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 are some misunderstanding.
leader-schedule-limit
andregion-schedule-limit
does need in previous and current version to reduce the schedule. I'll update the comment later.- Before Persist temporary setting to etcd tikv/pd#3131
leader-schedule-limit
andregion-schedule-limit
doesn't support ttl second. I think we should wait PD merge 3131 then test.
I want to make sure this PR is compatible with the old BR version and easy to support set pd ttl config. I'll file another PR to update config when 3131 merged.
Co-authored-by: kennytm <kennytm@gmail.com>
/rebuild |
/rebuild |
/rebuild |
1 similar comment
/rebuild |
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.
rest LGTM but that's a big rest.
/rebuild |
/run-integration-test |
3 similar comments
/run-integration-test |
/run-integration-test |
/run-integration-test |
/rebuild |
/run-integration-test |
LGTM |
cherry pick to release-4.0 in PR #596 |
* pdutil: use temp pause config * refactor pdutil * fix ci * add pd version fail back * fix ci * fix ci * fix unmarshal bool * address comment * fi * add test case * Apply suggestions from code review Co-authored-by: kennytm <kennytm@gmail.com> * address comment * fix ci * update comment * update comment * Update pkg/pdutil/pd.go Co-authored-by: kennytm <kennytm@gmail.com> * address comment * change convoluted logic * resume config by set ttlSecond to 0 * test pause config * fix failpoint * update test * fix test Co-authored-by: luancheng <luancheng@pingcap.com> Co-authored-by: kennytm <kennytm@gmail.com>
What problem does this PR solve?
After tikv/pd#3088 pd support set temporary config with ttlSecond. so BR can improve the behavior of pd config setting.
What is changed and how it works?
Check List
Tests
Code changes
Related changes
Release Note