From 84c6270a1b7803ef1080c1c834793b9e4b51eeb5 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Fri, 15 Dec 2023 19:59:06 +0800 Subject: [PATCH 1/3] Add temp.md --- temp.md | 1 + 1 file changed, 1 insertion(+) create mode 100644 temp.md diff --git a/temp.md b/temp.md new file mode 100644 index 0000000000000..af27ff4986a7b --- /dev/null +++ b/temp.md @@ -0,0 +1 @@ +This is a test file. \ No newline at end of file From a5668bb045cd5914dd310f276b4df63ec2509798 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Fri, 15 Dec 2023 19:59:12 +0800 Subject: [PATCH 2/3] Delete temp.md --- temp.md | 1 - 1 file changed, 1 deletion(-) delete mode 100644 temp.md diff --git a/temp.md b/temp.md deleted file mode 100644 index af27ff4986a7b..0000000000000 --- a/temp.md +++ /dev/null @@ -1 +0,0 @@ -This is a test file. \ No newline at end of file From 93741d66643e2c0e68034ac9ae9ab125ed1967d4 Mon Sep 17 00:00:00 2001 From: qiancai Date: Fri, 15 Dec 2023 20:02:55 +0800 Subject: [PATCH 3/3] Update troubleshoot-tidb-oom.md --- troubleshoot-tidb-oom.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/troubleshoot-tidb-oom.md b/troubleshoot-tidb-oom.md index 95c72e114a943..5362ba9f74b9c 100644 --- a/troubleshoot-tidb-oom.md +++ b/troubleshoot-tidb-oom.md @@ -19,7 +19,7 @@ The following are some typical OOM phenomena: - **TiDB-Runtime** > **Memory Usage** shows that the `estimate-inuse` metric keeps rising. - Check `tidb.log`, and you can find the following log entries: - - An alarm about OOM: `[WARN] [memory_usage_alarm.go:139] ["tidb-server has the risk of OOM. Running SQLs and heap profile will be recorded in record path"]`. For more information, see [`memory-usage-alarm-ratio`](/system-variables.md#tidb_memory_usage_alarm_ratio). + - An alarm about OOM: `[WARN] [memory_usage_alarm.go:139] ["tidb-server has the risk of OOM because of memory usage exceeds alarm ratio. Running SQLs and heap profile will be recorded in record path"]`. For more information, see [`memory-usage-alarm-ratio`](/system-variables.md#tidb_memory_usage_alarm_ratio). - A log entry about restart: `[INFO] [printer.go:33] ["Welcome to TiDB."]`. ## Overall troubleshooting process @@ -189,7 +189,7 @@ To locate the root cause of an OOM issue, you need to collect the following info - Run `grep "tidb-server has the risk of OOM" tidb.log` to check the path of the alert file collected by TiDB Server. The following is an example output: ```shell - ["tidb-server has the risk of OOM. Running SQLs and heap profile will be recorded in record path"] ["is tidb_server_memory_limit set"=false] ["system memory total"=14388137984] ["system memory usage"=11897434112] ["tidb-server memory usage"=11223572312] [memory-usage-alarm-ratio=0.8] ["record path"="/tmp/0_tidb/MC4wLjAuMDo0MDAwLzAuMC4wLjA6MTAwODA=/tmp-storage/record"] + ["tidb-server has the risk of OOM because of memory usage exceeds alarm ratio. Running SQLs and heap profile will be recorded in record path"] ["is tidb_server_memory_limit set"=false] ["system memory total"=14388137984] ["system memory usage"=11897434112] ["tidb-server memory usage"=11223572312] [memory-usage-alarm-ratio=0.8] ["record path"="/tmp/0_tidb/MC4wLjAuMDo0MDAwLzAuMC4wLjA6MTAwODA=/tmp-storage/record"] ``` ## See also