-
Notifications
You must be signed in to change notification settings - Fork 312
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
playground: Supports TiKV-CDC component #2000
Conversation
Signed-off-by: pingyu <yuping@pingcap.com>
Signed-off-by: pingyu <yuping@pingcap.com>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Codecov ReportBase: 52.51% // Head: 46.40% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #2000 +/- ##
==========================================
- Coverage 52.51% 46.40% -6.11%
==========================================
Files 308 308
Lines 35946 36070 +124
==========================================
- Hits 18875 16738 -2137
- Misses 14849 17152 +2303
+ Partials 2222 2180 -42
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Signed-off-by: pingyu <yuping@pingcap.com>
Signed-off-by: pingyu <yuping@pingcap.com>
Signed-off-by: pingyu <yuping@pingcap.com>
if c.ConfigPath != "" { | ||
args = append(args, fmt.Sprintf("--config=%s", c.ConfigPath)) | ||
} | ||
args = append(args, fmt.Sprintf("--data-dir=%s", filepath.Join(c.Dir, "data"))) |
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 line 66 be merged in line 56 constructor initialization?
tests/tiup-playground/test_kvcdc.sh
Outdated
killall -9 grafana-server || true | ||
killall -9 tiup-playground || true | ||
killall -9 prometheus || true | ||
killall -9 ng-monitoring-server || true |
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 tikv-cdc
be included?
Signed-off-by: pingyu <yuping@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~
@haojinming: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
@@ -44,6 +44,7 @@ const ( | |||
ComponentDrainer = "drainer" | |||
ComponentPump = "pump" | |||
ComponentCDC = "cdc" | |||
ComponentTiKVCDC = "tikv-cdc" |
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's the difference between cdc
and tikv-cdc
? This is added to the cluster/spec
package, so does tiup-cluster
need to be aware of the new component as well?
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.
tikv-cdc
is another CDC frame but focus on NoSQL scenario, while cdc
focus on SQL database. Please refer to https://github.com/tikv/migration/blob/main/cdc/README.md.
tiup-cluster
need to be aware of the new component as well, please see #2022.
tests/tiup-playground/test_kvcdc.sh
Outdated
outfile=/tmp/tiup-playground-test.out | ||
tiup mirror set $MIRROR | ||
# no tiflash to speed up | ||
tiup-playground $TIDB_VERSION --db 1 --pd 1 --kv 1 --tiflash 0 --kvcdc 1 --kvcdc.version $KVCDC_VERSION > $outfile 2>&1 & |
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.
Why not add this to the current playground
integration test? Adding a whole new integration test will add one more Github Actions job and make the CI run time much longer.
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.
OK let me try. I just thought that the separation will make the test easier to be maintained.
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.
It's not a must, so merging them or not is up to you.
If the new test takes long time to complete, it's better to make it a dedicate one, so that it can run parallel with other jobs, as I can see in the actions run result under this PR, the new job only takes 2~3min to complete, then adding it to the current one could save some time setting up the env in jobs & the time waiting for available runner host.
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.
Done. PTAL, thanks~
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~
@zeminzhou: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
Signed-off-by: pingyu <yuping@pingcap.com>
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 6f5d5a7
|
What problem does this PR solve?
Close #1999: playground: Support component TiKV-CDC.
What is changed and how it works?
Add codes to deal with deploy, scale-in and scale-out of the TiKV-CDC component.
Check List
Tests
deploy:
display
,scale-in
andscale-out
:Code changes
Add
Version
toinstance.Config
, to keep version of TiKV-CDC that can be specified by command line argument.Side effects
Related changes
Release notes: