How can we identify and manage long-running queries in TiDB v4.0.14 that cause high CPU usage and I/O operations, leading to potential bottlenecks in the TiDB cluster? Is there a way to find these queries and terminate them efficiently?
Hi @prateekrckstr , maybe ‘show process list’ works. Btw, you can also check the solution in this post: TiDB long running queries