From 8ee26517c79cef672119741da36ef8861a67300f Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Wed, 26 Jun 2024 16:16:22 +0800 Subject: [PATCH] =?UTF-8?q?troubleshoot-tidb-oom=EF=BC=9Aupdate=20the=20in?= =?UTF-8?q?correct=20command,=20add=20double=20quotes=20(#18027)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- troubleshoot-tidb-oom.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/troubleshoot-tidb-oom.md b/troubleshoot-tidb-oom.md index 5362ba9f74b9c..1c2f102cd0681 100644 --- a/troubleshoot-tidb-oom.md +++ b/troubleshoot-tidb-oom.md @@ -183,7 +183,7 @@ To locate the root cause of an OOM issue, you need to collect the following info - Run the following command to collect the TiDB Profile information when memory usage is high: ```shell - curl -G http://{TiDBIP}:10080/debug/zip?seconds=10" > profile.zip + curl -G "http://{TiDBIP}:10080/debug/zip?seconds=10" > profile.zip ``` - 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: