pingcap / pingcap/ticdc

Missing logs for automatic Safe Mode entry and exit

Open
#2,898 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type/enhancement
Dominant language
Go
Stars
56
Forks
63
Avg merge
2d 20h
Merged PRs (30d)
34

Description

Currently, when the system automatically enters or exits Safe Mode, no related logs are printed.
These logs are very helpful when investigating issues such as unexpected Safe Mode activation or failure to exit Safe Mode properly.

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 Go code that automatically enters and exits Safe Mode, then review the project's existing logging conventions nearby. Done means both automatic transitions emit useful logs that help diagnose unexpected activation and failure to exit.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.