Should TiCDC continue replicating data during rolling update #3261
Labels
area/ticdc
Issues or PRs related to TiCDC.
status/need-discussion
Issue that needs to be discussed to confirm priority, milestone, plan and task breakdown.
subject/new-feature
Denotes an issue or pull request adding a new feature.
Comments
amyangfei
added
subject/new-feature
|
Solved by #4757 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
For example if we deploy a TiDB cluster across three AZs to achieve high availability, and also deploy one TiCDC server in each AZ to replicate data from TiDB to downstream.
We we want to upgrade the TiDB cluster, we could perform a rolling upgrade for servers one by one, in the order of AZ.
Since the rolling upgrade of TiKV could be very slow (as long as hours), there will exist different versions of TiCDC in the whole cluster for quite a long time. During that time, TiCDC refuses to replicate data because of strict version check, ref:
https://github.com/pingcap/ticdc/blob/6655bf0835c8bbd31d949b7c8da79bf09e6f5a3c/cdc/owner/owner.go#L271-L280
Describe the feature you'd like
Loosen the version check strategy, such as when upgrading TiCDC from
v5.2.2tov5.2.3, TiCDC can continue replicate during rolling upgrade.Describe alternatives you've considered
No response
Teachability, Documentation, Adoption, Migration Strategy
No response
The text was updated successfully, but these errors were encountered: