-
Notifications
You must be signed in to change notification settings - Fork 500
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
binlog: support binlog.pump.config
configurations for pump and drainer
#693
Conversation
charts/tidb-cluster/values.yaml
Outdated
heartbeat-interval = 2 | ||
[storage] | ||
sync-log = true | ||
stop-write-at-available-space = "100 gib" |
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.
# stop write when disk available space less then the configured size
# 42 MB -> 42000000, 42 mib -> 44040192
# default: 10 gib
# stop-write-at-available-space = "10 gib"
I think it should be 1 Gigabytes or less
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.
Yes, this is available space size, using default.
charts/tidb-cluster/values.yaml
Outdated
# drainer configurations (change to the tags of your drainer version), | ||
# just follow the format in the file and configure in the 'config' section | ||
# as below if you want to customize any configuration. | ||
config: | |
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.
This causes the old configuration key invalid, which is an in-compatible change
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.
I think we should document a migration guide for RC and beta users
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 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.
What about we keep these two ways, but make it clear in the document that we do not maintain the config for the original way and users should migrate to the new way if they want to configure any new parameters that are not exposed in values.yaml.
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.
Have we decided to make this change incompatible?
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.
What do you think? @tennix
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.
Agree with @DanielZhangQD we should not make this incompatible change.
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.
I think we can keep both for binlog configurations to keep compatible.
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.
comments addressed.
I think rollout the binlog configuration is not a small change, can we put this to 1.1? |
/run-e2e-tests |
@@ -26,6 +26,7 @@ done | |||
|
|||
/drainer \ | |||
-L={{ .Values.binlog.drainer.logLevel | default "info" }} \ | |||
-pd-urls={{ template "cluster.name" . }}-pd:2379 \ |
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.
add http://
scheme
@@ -1,5 +1,6 @@ | |||
set -euo pipefail | |||
/pump \ | |||
-pd-urls={{ template "cluster.name" . }}-pd:2379 \ |
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.
ditto
/run-e2e-tests |
2 similar comments
/run-e2e-tests |
/run-e2e-tests |
…ator into weekface/binlog-config
/run-e2e-tests |
/run-e2e-tests |
1 similar comment
/run-e2e-tests |
f5386d6
to
4f300a4
Compare
/run-e2e-in-kind |
1 similar comment
/run-e2e-in-kind |
/run-e2e-in-kind |
f8bbb58
to
1c33136
Compare
@aylei @DanielZhangQD @tennix @xiaojingchen This PR changed to support both configurations. PTAL again. |
/run-e2e-in-kind |
binlog.pump.config
and binlog.drainer.config
configurations for pump and drainer
binlog.pump.config
and binlog.drainer.config
configurations for pump and drainer binlog.pump/drainer.config
configurations for pump and drainer
binlog.pump/drainer.config
configurations for pump and drainer binlog.pump.config
configurations for pump and drainer
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.
Co-Authored-By: Tennix <tennix@users.noreply.github.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
/run-e2e-in-kind |
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
cherry pick to release-1.1 failed |
cherry pick to release-1.0 failed |
…ner (pingcap#693) (cherry picked from commit a320e52)
What problem does this PR solve?
binlog.pump.config
andbinlog.drainer.config
configurations for pump and drainerWhat is changed and how does it work?
Check List
Tests
Code changes
Side effects
Related changes
Does this PR introduce a user-facing change?: