skills.rest
alex-quan-001
alex-quan-001COMMUNITY
Explore all skills by this author →
GitHub

tikv-cdc

Diagnose TiKV and TiCDC interaction failures with curated root cause guidance.

Updated Jun 3, 2026
Search Tags:#diagnosis#scaling#on-call#tidb#ticdc#changefeed#tikv
One-click install
npx skills add https://github.com/alex-quan-001/nutshell-skills --skill tikv-cdc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tikv-cdc
Source: https://github.com/alex-quan-001/nutshell-skills/tree/main/skills/diagnosis/tikv-cdc
Command: npx skills add https://github.com/alex-quan-001/nutshell-skills --skill tikv-cdc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork and lengthy investigation time for troubleshooting complex TiKV and TiCDC interaction failures, giving on-call engineers clear, curated guidance to resolve incidents faster.

Core Features & Use Cases

  • Curated Known Failure Patterns: Access documented, real-world cases of common TiKV-TiCDC issues including CDC-triggered TiKV panics, changefeed lag after cluster scaling, and stale PD/store endpoint reuse, each with workarounds and related incident references.
  • Targeted Diagnostic Workflow: Follow structured first checks to quickly differentiate between CDC metadata drift and TiKV runtime state root causes, reducing time spent on irrelevant troubleshooting steps.
  • Deep Dive References: Access extended, detailed breakdowns of complex issues like TiKV address reuse-induced changefeed lag for more in-depth investigation when needed. Use Case: For example, if your TiCDC changefeeds are experiencing increasing lag after a TiKV scale-out operation, this Skill helps you quickly identify if the root cause is stale store ID metadata and apply the correct restart workaround.

Quick Start

Use the tikv-cdc skill to investigate your TiKV-TiCDC interaction failure, identify the root cause, and apply the recommended workaround.

Frequently Asked Questions about tikv-cdc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does TiCDC changefeed lag increase after scaling out a TiKV cluster?▼

TiCDC changefeed lag after TiKV scale-out often stems from stale store ID metadata or endpoint reuse. This diagnostic workflow identifies if address reuse causes the lag and provides the correct restart workaround.

How do I diagnose a TiKV panic triggered by TiCDC lock handling?▼

Diagnosing a TiKV panic triggered by TiCDC lock handling requires checking curated known failure patterns. You can differentiate between CDC metadata drift and TiKV runtime state anomalies to pinpoint the root cause.

How do I differentiate between CDC metadata drift and TiKV runtime state anomalies?▼

Differentiating between CDC metadata drift and TiKV runtime state anomalies involves following structured first checks. This targeted diagnostic workflow isolates whether the synchronization failure originates from store metadata or storage layer runtime.

Can I use this troubleshooting workflow for TiDB Cloud and on-premises clusters?▼

This troubleshooting workflow applies to both TiDB Cloud and on-premises TiDB clusters. It supports on-call engineering workflows to resolve CDC synchronization issues and store metadata drift across different environments.

What are common TiKV and TiCDC interaction failures during on-call incidents?▼

Common TiKV and TiCDC interaction failures include CDC-triggered TiKV panics, changefeed lag after cluster scaling, and stale PD or store endpoint reuse. These known patterns provide workarounds to reduce incident resolution time.

How do I fix stale PD or store endpoint reuse causing changefeed lag?▼

Fixing stale PD or store endpoint reuse involves applying a specific restart workaround once the address reuse is identified. The skill provides deep dive references and extended breakdowns for this specific changefeed lag issue.

Related Skills

Explore More Software Engineering Skills→
alex-quan-001alex-quan-001

ticdc-next-gen-deploy

Deploy and destroy TiCDC next-gen test stacks via SSH with TiUP.

Community
Advanced
alex-quan-001alex-quan-001

tikv-status-server

Diagnose TiKV status server access failures and profiling issues.

Community
Intermediate
alex-quan-001alex-quan-001

ticdc-health-inspection

Audit TiCDC runtime health with architecture-aware metric rules.

Community
Advanced
alex-quan-001alex-quan-001

tikv-raftstore

Diagnose TiKV raftstore and region lifecycle incidents with diagnostic patterns and workarounds.

Community
Intermediate