Troubleshooting TiDB Server

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

Original topic: TiDB-server故障排查

| username: TiDBer_CkS2lbTx

Where can I see the logs when TiDB-server encounters an OOM during operation, or which monitoring module in Prometheus can observe it? Is the OOM mostly caused by slow SQL?

| username: caiyfc | Original post link

The TiDB-server experiencing OOM is mostly caused by slow SQL queries. To determine if it is an OOM issue, you can check here: TiDB OOM Troubleshooting | PingCAP Documentation Center

| username: tidb菜鸟一只 | Original post link

You can just look at the TiDB logs.

| username: Miracle | Original post link

You can check TiDB logs and the system logs of the operating system.
For monitoring, you can look at the overview panel in Grafana.
Most OOM (Out of Memory) issues are caused by slow SQL queries.

| username: redgame | Original post link

It is generally due to an inefficient SQL execution plan, lack of appropriate indexes, outdated statistics, or optimizer bugs.

| username: TiDBer_aaO4sU46 | Original post link

I mostly know about major things, mainly SQL-related stuff.

| username: TiDBer_CkS2lbTx | Original post link

Will TiKV also experience OOM (Out of Memory)?

| username: Jolyne | Original post link

Search for “out of memory” on the dashboard or the machine where tidb-server is deployed.

| username: caiyfc | Original post link

It is possible. If the capacity parameter is set correctly, TiKV will basically not encounter OOM situations.

| username: DBAER | Original post link

Check TiDB logs

| username: zhanggame1 | Original post link

Memory is not too small, and it won’t be an issue if not deployed in a mixed environment.

| username: dba远航 | Original post link

TiDB-server encountered OOM, which in most cases is caused by large SQL queries.

| username: system | Original post link

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