From d4b69ab5fa431d46e01f34e31e9a07faf4bb9e75 Mon Sep 17 00:00:00 2001 From: lilin90 Date: Fri, 1 Nov 2024 16:35:23 +0800 Subject: [PATCH] Update capitalization --- tiflash/tiflash-mintso-scheduler.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tiflash/tiflash-mintso-scheduler.md b/tiflash/tiflash-mintso-scheduler.md index bd82ae5bfcad3..6b1ec017863ba 100644 --- a/tiflash/tiflash-mintso-scheduler.md +++ b/tiflash/tiflash-mintso-scheduler.md @@ -46,7 +46,7 @@ EXPLAIN SELECT count(*) FROM t0 a JOIN t0 b ON a.id = b.id; +--------------------------------------------+----------+--------------+---------------+----------------------------------------------------------+ ``` -For example, the above query generates 2 MPP Tasks on each TiFlash node, where the MPP Task containing `ExchangeSender_45` depends on the MPP Task containing `ExchangeSender_21`. In high concurrency scenarios, if the scheduler schedules the MPP Task containing `ExchangeSender_45` for each query, the system will enter a deadlock state. +For example, the preceding query generates 2 MPP tasks on each TiFlash node, where the MPP Task containing `ExchangeSender_45` depends on the MPP Task containing `ExchangeSender_21`. In high concurrency scenarios, if the scheduler schedules the MPP Task containing `ExchangeSender_45` for each query, the system will enter a deadlock state. To avoid deadlock, TiFlash introduces the following two levels of thread limits: