pingcap / pingcap/tidb

global sort split range take a long time

Open
#50,610 2 comments 0 reactions 0 assignees View on GitHub
component/ddl type/enhancement
Dominant language
Go
Stars
40.5k
Forks
6.2k
PR merge metrics
PR metrics pending

Description

## Bug Report

Please answer these questions before submitting your issue. Thanks!

### 1. Minimal reproduce step (Required)
global sort add index for a 120T table
you can see after step 1,2 , there is only 1 tidb node works for a long time
![图片](https://github.com/pingcap/tidb/assets/10184437/2adaf142-2ceb-49c7-aea6-36ac087f57a7)

### 2. What did you expect to see? (Required)

### 3. What did you see instead (Required)

### 4. What is your TiDB version? (Required)
master https://github.com/pingcap/tidb/commit/6db1d6b79c2855cf022f04ced86af3e6bc8b0dcf

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the global sort add-index operation on a 120T table at commit 6db1d6b79c2855cf022f04ced86af3e6bc8b0dcf. Observe the TiDB nodes during the split-range steps and determine why only one node remains active; the issue needs expected behavior and a precise completion condition before implementation can begin.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases, distributed-systems, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.