IO snooper is not started due to not compiling with BCC

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: IO snooper is not started due to not compiling with BCC

| username: kuweilong666

[TiDB Usage Environment] Production Environment
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
TiKV node crashed

image
image1298×237 8.66 KB

[Encountered Issue: Issue Phenomenon and Impact]

image
image1551×622 34.3 KB

[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

2
| username: 啦啦啦啦啦 | Original post link

Check if there is enough disk space.

3
| username: kuweilong666 | Original post link

There are still 2TB of remaining disk space.

4
| username: Soysauce520 | Original post link

Is there a size limit for TiKV parameters?

5
| username: kuweilong666 | Original post link

The process on the crashed node is still running. After restarting the machine, TiKV was restarted.

6
| username: kuweilong666 | Original post link

TiKV uses default parameters and has not been configured.

7
| username: WalterWj | Original post link

Scale up or down to fix it.

You can check the system logs of this tikv node for any IO errors. However, looking at the tikv logs, it seems there might be an issue with this region :thinking:.

8
| username: kuweilong666 | Original post link

Can we directly shrink this node first and then expand it back in?

9
| username: WalterWj | Original post link

No, if the number of nodes is less than the number of replicas, you can’t scale down.

10
| username: kuweilong666 | Original post link

Which one is the system log?

11
| username: Min_Chen | Original post link

Hello,
It should be an SST file corruption. You can follow the suggestion above to scale in and out to fix it.
Since you currently have only three TiKV nodes, you can scale out first and then scale in.

12
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.