pingcap/tiflow

dm: let syncer wait relay catch up

Open

#3,379 opened on Nov 10, 2021

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Go (310 forks)auto 404
area/dmhelp wantedsubject/new-feature

Repository metrics

Stars
 (461 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem?

see discuss in #3365

most time it's not a problem, but may cause some integration cases fail

Describe the feature you'd like

solutions:

  • let relay catch up before restart syncers
  • syncer fails with a less severe error, try again internally and does not pause

Describe alternatives you've considered

No response

Teachability, Documentation, Adoption, Migration Strategy

No response

Contributor guide

Research direction
Study the code for DM syncer and relay to understand how they interact. Identify where the syncer starts and how it can wait for relay catch up. Consider implementing a wait condition or internal retry logic.
Tech stack
go
Domain
backenddata
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60