Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: Tiflash OOM 频繁重启
【TiDB Usage Environment】Production Environment
【TiDB Version】V6.2.0
【Encountered Problem】tiflash OOM frequently restarts
【Reproduction Path】alter table dataname.xxxx SET TIFLASH REPLICA 1; After adding the replica and completing synchronization, OOM starts to occur
【Problem Phenomenon and Impact】
【Attachments】Related logs and monitoring (https://metricstool.pingcap.com/)
Basic monitoring
Region
Server
Raft
tiflash related parameter configuration (default configuration)
Check if the continuous profiling in the dashboard diagnostics is enabled. Try turning it off.
It’s already turned off. I’ll observe for a while longer.
The problem still exists after turning off continue profiling.
Please send the TiFlash logs.
Could it be because this partitioned table is too large?
Is there a query at the time of OOM?
There was an OOM around 15:38 in the East 8th District.
The time range of this log is more reasonable, including OOM.
tiflash_172.31.14.22_3930_1.log (9.9 MB)
Looking at the logs, there was nothing unusual before the OOM, but the monitoring shows a sudden increase in memory usage. It is confirmed that there was a large table query at that time as you mentioned.
From the known bugs, if OOM does not occur after a restart, it is generally caused by a query.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: Jennie
|
username: 
|
username: 
|
username: