tikv-status-server

Diagnose TiKV status server access failures and profiling issues.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/alex-quan-001/nutshell-skills --skill tikv-status-server
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tikv-status-server
Source: https://github.com/alex-quan-001/nutshell-skills/tree/main/skills/diagnosis/tikv-status-server
Command: npx skills add https://github.com/alex-quan-001/nutshell-skills --skill tikv-status-server

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

On-call engineers often face hard-to-debug TiKV status port access failures, pprof deadlocks, profile collection errors, file descriptor leaks, and slow backtrace collection that require specialized reference knowledge to resolve quickly, reducing incident response time.

Core Features & Use Cases

  • Known Issue Reference: Curated documentation of common TiKV status server and profiling failure patterns, including root causes, workarounds, and fixed version information.
  • Troubleshooting Guidance: Step-by-step checks for access failures, TLS mismatches, and profiling side effects to narrow down incident root causes faster.
  • Use Case: If your TiKV cluster's status port is inaccessible due to TLS handshake errors, this skill provides the exact root cause and client-side configuration fix to restore access in minutes.

Quick Start

Use the tikv-status-server skill to diagnose the root cause of your TiKV status port access failure or profiling collection issue and get the corresponding workaround.

Frequently Asked Questions about tikv-status-server

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

FAQPage Schema
Why is my TiKV status port inaccessible due to TLS handshake errors?

TiKV status port access failures from TLS handshake errors often stem from client-side configuration mismatches. This skill provides the exact root cause and client-side configuration fix to restore access in minutes.

How do I fix pprof deadlocks and slow backtrace collection in TiKV?

Pprof deadlocks and slow backtrace collection in TiKV are known profiling side effects. This skill offers documented known cases, root causes, and workarounds to resolve these runtime profiling issues faster.

What causes file descriptor leaks during TiKV profile collection?

File descriptor leaks during TiKV profile collection are common profiling failure patterns. This skill curates known issue references with root causes, workarounds, and fixed version information to resolve the leaks.

Can I use this diagnosis workflow for both TiDB Cloud and on-premises TiKV clusters?

Yes, this skill covers both TiDB Cloud and on-premises TiKV cluster diagnosis scenarios. It provides step-by-step troubleshooting checks for status port connectivity and performance issues across both environments.

How do I troubleshoot TiKV status server access failures step by step?

Troubleshoot TiKV status server access failures by following step-by-step checks for TLS mismatches and profiling side effects. This skill helps narrow down incident root causes to reduce on-call response time.

What are the limitations when diagnosing TiKV runtime profiling issues?

Limitations when diagnosing TiKV runtime profiling issues include hard-to-debug profile collection errors and pprof deadlocks. This skill provides documented fixed version references to identify when a known limitation is resolved.