pingcap / pingcap/tidb-binlog

support to specify downstream host with multiple IPs

Open
#1,013 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request
Dominant language
Go
Stars
291
Forks
131
Avg merge
5m
Merged PRs (30d)
2

Description

Feature Request

Is your feature request related to a problem? Please describe:

When one downsteam IP is down , drainer can retry others IPs

Describe the feature you'd like:

Support to drainer syncer.to mysql host as multiple IP:

[syncer.to]
host = "127.0.0.1,192.168.0.1,192.168.0.100"

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the drainer syncer.to configuration and the code that connects to the MySQL host. Verify how a comma-separated host is parsed and how connection retries currently behave. Done means an unavailable IP can fall back to another configured IP without breaking existing single-host configurations.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, mysql
Domain
backend, databases, networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.