SST Missing Investigation FAQs

Question 1

Can it analyze compressed log files?

Accepted Answer

Yes, the skill is configured to use 'rg -z' which allows it to search through .gz log files without requiring manual decompression, saving time and disk space.

Question 2

What is a missing SST incident in TiDB?

Accepted Answer

It occurs when a component like TiFlash or TiKV attempts to read an SST (Sorted String Table) file from S3 that has been prematurely deleted or misplaced, resulting in a NoSuchKey error.

Question 3

What evidence does the skill provide for the final report?

Accepted Answer

It generates an investigate.md file containing a distilled summary, per-pod mappings, a chronological timeline, and raw log lines with exact file and line number references.

Question 4

How does this skill automate the investigation process?

Accepted Answer

The skill uses optimized search commands (like ripgrep) to scan logs across all pods, extracting shard IDs and region metadata to map exactly when and where an SST file was last seen or deleted.

Question 5

How does it handle different time zones in logs?

Accepted Answer

The skill includes logic to normalize timestamps, specifically converting s3clean UTC+0 records to the cluster's local time (e.g., UTC+8) to ensure accurate event correlation.

SST Missing Investigation

Características Principales

Casos de Uso

SST Missing Investigation

Características Principales

Casos de Uso