Skip to content

Conversation

@3pointer
Copy link
Contributor

@3pointer 3pointer commented Feb 2, 2026

Summary

This PR adds TiCI (meta/worker) as a first‑class component in TidbCluster, wires it into the controller sync loop, integrates TiFlash with TiCI config, and provides an end‑to‑end example (including MinIO + FTS verification) for local testing.

For more details about how to run tici via tidb-operator: please refer to examples/tici/readme.md

Key Changes

  • API/Spec/Status
    • Added TiCI spec/status, new member types, labels, defaulting, and validation.
  • Controller/Manager
    • New TiCI member manager to create services, configmaps, and statefulsets for meta/worker.
    • Integrated TiCI sync into the control loop.
  • TiFlash integration
    • Injected TiCI config into TiFlash; reader now binds to a literal IP and advertises the pod DNS.
    • Added log routing option to stdout for searchlib.
  • Volumes
    • Added TiCI member types to volume modifier.
    • Avoided PVC VolumeName lookups when unset.
  • Examples
    • New examples/tici/ with tici-tc.yaml and README (MinIO + FTS verification flow).

##Testing

  • Not run in CI.
  • Manual verification flow documented in examples/tici/README.md.

Notes / Operational Considerations

  • TiFlash TiCI reader requires a literal bind address; hostname-only addresses cause startup failures.
  • On kind/podman, pod PID limits must be removed (TasksMax/infinity) to avoid newosproc.
  • If reusing old TiFlash PVs, PD may reject duplicated store addresses; wipe PVC or delete the store.

Follow‑ups

  • Consider formalizing TiCDC changefeed creation for TiCI if desired.
  • Add unit tests for TiCI manager and config rendering.

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Feb 2, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@codecov-commenter
Copy link

codecov-commenter commented Feb 2, 2026

Codecov Report

❌ Patch coverage is 5.76471% with 801 lines in your changes missing coverage. Please review.
⚠️ Please upload report for BASE (release-1.x@9ab6710). Learn more about missing BASE report.

Additional details and impacted files
@@              Coverage Diff               @@
##             release-1.x    #6699   +/-   ##
==============================================
  Coverage               ?   56.42%           
==============================================
  Files                  ?      266           
  Lines                  ?    39210           
  Branches               ?        0           
==============================================
  Hits                   ?    22124           
  Misses                 ?    15002           
  Partials               ?     2084           
Flag Coverage Δ
unittest 56.42% <5.76%> (?)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@liubog2008
Copy link
Member

please submit pr to release-1.x

@liubog2008 liubog2008 changed the base branch from release-1.6 to release-1.x February 2, 2026 09:52
Copy link

@JaySon-Huang JaySon-Huang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Feb 9, 2026

@JaySon-Huang: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

lgtm

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 kubernetes-sigs/prow repository.

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Feb 9, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: JaySon-Huang
Once this PR has been reviewed and has the lgtm label, please assign aylei for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@3pointer 3pointer marked this pull request as ready for review February 11, 2026 08:35
@ti-chi-bot ti-chi-bot bot requested a review from shonge February 11, 2026 08:35
common.SetIfNil("flash.tidb_status_addr", tidbStatusAddr)
if !mountCMInTiflashContainer {
common.SetIfNil("flash.service_addr", fmt.Sprintf("%s:%d", listenHost, v1alpha1.DefaultTiFlashFlashPort))
common.SetIfNil("flash.service_addr", fmt.Sprintf("%s-POD_NUM.%s.%s.svc%s:%d",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This may cause existing TiFlash pods to be recreated after upgrading the TiDB Operator.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for pointing this out. I changed flash.service_addr in getTiFlashConfigV2 to be conditional: for non-TiCI clusters it keeps the previous value (listenHost:3930, e.g. 0.0.0.0:3930) to avoid unnecessary TiFlash pod recreation on operator upgrade; when TiCI is enabled (spec.tici.s3 configured) it uses the new headless service address.

region: us-east-1
accessKey: ""
secretKey: ""
bucket: tici_test
Copy link
Contributor Author

@3pointer 3pointer Feb 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"_" is invalid in gcs bucket name

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed. I changed the GCS bucket example from tici_test to tici-test and updated the corresponding sinkURI to match. I also aligned the related docs/examples to use the same valid bucket name consistently.

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Feb 12, 2026

@3pointer: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-e2e-kind-br f5fe44e link false /test pull-e2e-kind-br
pull-e2e-kind-scale-simultaneously f5fe44e link false /test pull-e2e-kind-scale-simultaneously
pull-e2e-kind-serial f5fe44e link false /test pull-e2e-kind-serial
pull-e2e-kind-across-kubernetes f5fe44e link false /test pull-e2e-kind-across-kubernetes
pull-e2e-kind-tngm f5fe44e link false /test pull-e2e-kind-tngm
pull-e2e-kind-basic f5fe44e link false /test pull-e2e-kind-basic
pull-e2e-kind-tidbcluster f5fe44e link false /test pull-e2e-kind-tidbcluster
pull-e2e-kind-dmcluster f5fe44e link false /test pull-e2e-kind-dmcluster

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants