This repository has been archived by the owner on Nov 24, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 188
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
amyangfei
added
priority/important
Major change, requires approval from ≥2 primary reviewers
status/PTAL
This PR is ready for review. Add this label back after committing new changes
type/enhancement
Performance improvement or refactoring
needs-cherry-pick-release-1.0
This PR should be cherry-picked to release-1.0. Remove this label after cherry-picked to release-1.0
needs-update-release-note
This PR should be added into release notes. Remove this label once the release notes are updated
labels
Sep 10, 2019
csuzhangxc
reviewed
Sep 10, 2019
csuzhangxc
reviewed
Sep 10, 2019
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.
LGTM
csuzhangxc
added
status/LGT1
One reviewer already commented LGTM
and removed
status/PTAL
This PR is ready for review. Add this label back after committing new changes
labels
Sep 10, 2019
Codecov Report
@@ Coverage Diff @@
## master #280 +/- ##
===========================================
Coverage ? 60.0027%
===========================================
Files ? 134
Lines ? 14766
Branches ? 0
===========================================
Hits ? 8860
Misses ? 5060
Partials ? 846 |
WangXiangUSTC
added
status/LGT2
Two reviewers already commented LGTM, ready for merge
and removed
status/LGT1
One reviewer already commented LGTM
labels
Sep 10, 2019
WangXiangUSTC
approved these changes
Sep 10, 2019
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.
LGTM
amyangfei
added a commit
to amyangfei/dm
that referenced
this pull request
Sep 10, 2019
amyangfei
added a commit
that referenced
this pull request
Sep 10, 2019
Merged
amyangfei
added
already-cherry-pick-1.0
The related PR is already cherry-picked to release-1.0. Add this label once the PR is cherry-picked
already-update-release-note
The release note is updated. Add this label once the release note is updated
and removed
needs-cherry-pick-release-1.0
This PR should be cherry-picked to release-1.0. Remove this label after cherry-picked to release-1.0
needs-update-release-note
This PR should be added into release notes. Remove this label once the release notes are updated
labels
Sep 23, 2019
lichunzhu
pushed a commit
to lichunzhu/dm
that referenced
this pull request
Apr 6, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
already-cherry-pick-1.0
The related PR is already cherry-picked to release-1.0. Add this label once the PR is cherry-picked
already-update-release-note
The release note is updated. Add this label once the release note is updated
priority/important
Major change, requires approval from ≥2 primary reviewers
status/LGT2
Two reviewers already commented LGTM, ready for merge
type/enhancement
Performance improvement or refactoring
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?
currently we use a single
sql.DB
connection pool for multiple concurrent executors in single DM-worker, each time one a txn is committed, the connection will be tried to put back to the idle connection pool. Too small idle connection pool size will lead to rejection of the put-back and database too many connections re-create.What is changed and how it works?
set database MaxIdleConns according to worker-count
Check List
Tests
Code changes
Side effects
Related changes