pingcap / pingcap/tiflash

tombston is blocking all queries for tiflash

Open
#8,039 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component/storage severity/moderate type/bug
Dominant language
C++
Stars
1k
Forks
423
Avg merge
1d 15h
Merged PRs (30d)
24

Description

使用聚集索引的多partiton分区表 同步到tiflash

发现如果有一个表在执行ddl 处理时 会阻塞掉所有的 tiflash的sleect 操作. 必须等待所有的tiflash 的tombstone完成才可以执行

版本为 6.5.3 分区数大约在2000-3000 左右.

感谢.

2023-08-30 10:02:59 (UTC+08:00)TiFlash 192.168.255.121:3931[SchemaBuilder.cpp:1169] ["Tombstoned table db_327459.t_380193(380193)"] [source=SchemaBuilder] [thread_id=740]
2023-08-30 10:02:59 (UTC+08:00)TiFlash 192.168.255.121:3931[SchemaBuilder.cpp:1154] ["Tombstoning table db_327459.t_380194(380194)"] [source=SchemaBuilder] [thread_id=740]

2023-08-30 10:02:59 (UTC+08:00)TiFlash 192.168.255.121:3931[StorageDeltaMerge.cpp:115] ["updateTableColumnInfo: TableName t_380195 ordinary columns format version: 1\n322

会一直提示如下的内容.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the TiFlash logs from SchemaBuilder.cpp and StorageDeltaMerge.cpp for the reported 6.5.3 case with 2,000–3,000 partitions. Trace how DDL handling and table tombstoning interact with concurrent SELECT operations. Done means identifying and fixing the blocking behavior so TiFlash queries are not all blocked while tombstones complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.