pingcap / pingcap/tidb-binlog

Pump will retry to connect to the TiKV which is offline all the time

Open
#985 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

severity/moderate type/bug
Dominant language
Go
Stars
291
Forks
131
Avg merge
5m
Merged PRs (30d)
2

Description

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?

Offline a TiKV,

  1. What did you expect to see?

Pump can run normally.

  1. What did you see instead?

Pump send requests to the TiKV for check transaction's status, and will get warn log like below:

image

Pump can't get result from this TiKV, and will be blocked, so the Pump's usage memory will increase.

  1. Please provide the relate downstream type and version of drainer.
    (run drainer -V in terminal to get drainer's version)

v3.0.5

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 reproducing the issue with a TiKV taken offline, then inspect Pump's path for checking transaction status and the warning shown in the report. Done means Pump does not remain blocked or continuously grow its memory while the TiKV stays offline.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
distributed-systems
Issue type
Bug
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.