-
Notifications
You must be signed in to change notification settings - Fork 410
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
support to adjust max inflight msgs #450
Conversation
f311a74
to
0fa1d13
Compare
Signed-off-by: qupeng <qupeng@pingcap.com>
741695c
to
d9ffd50
Compare
Signed-off-by: qupeng <qupeng@pingcap.com>
Signed-off-by: qupeng <qupeng@pingcap.com>
Signed-off-by: qupeng <qupeng@pingcap.com>
@jayzhan211 could you take a look again? |
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
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
Signed-off-by: qupeng <qupeng@pingcap.com>
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
6a1c10e
to
339abf3
Compare
Signed-off-by: qupeng <qupeng@pingcap.com>
339abf3
to
91a8237
Compare
Signed-off-by: qupeng <qupeng@pingcap.com>
Signed-off-by: qupeng qupeng@pingcap.com
Sometimes we want to custom
max-inflight-msgs
for a given peer. For example, the target peer's memory or disk usage is almost full. This PR allows this.BTW a bug in
inflight_buffers_size
is fixed. With the patch its return value is real size instead of length.