The index acceleration JOB_TYPE column's ingest has changed to txn-merge, what does it mean?

Translated
1

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

Original topic: 索引加速JOB_TYPE 一列中的 ingest变成txn-merge了，啥意思？

| username: 我是咖啡哥

【TiDB Usage Environment】Production Environment / Testing / Poc
【TiDB Version】v6.5.0
【Reproduction Path】
A table with 460 million rows, testing the index acceleration feature of version 6.5.
Set tidb_ddl_reorg_worker_cnt to 32.
Observe the progress through admin show ddl jobs; initially, the job_type column shows add index /* ingest /, but after a few seconds, it changes to: add index / txn-merge */

image
image1380×568 220 KB

At the same time, the /tmp/tidb/ directory /tmp/tidb/tmp_ddl-4000 is no longer used.
image
image730×134 55.6 KB

Does this mean that the index acceleration feature is not being used?

The documentation says

  • To verify whether the completed ADD INDEX operation used the index acceleration feature, you can execute the ADMIN SHOW DDL JOBS statement and check if the JOB_TYPE column contains the word ingest.

【Encountered Problem: Problem Phenomenon and Impact】
admin show ddl jobs; the job_type column shows add index /* txn-merge */. What does this mean?
There is no relevant explanation found in the documentation.
【Resource Configuration】
A single-node physical machine.

2
| username: zhanggame1 | Original post link

I tested it,
tidb_ddl_reorg_worker_cnt = 12
The status is indeed add index /* ingest */
However, the data volume is too small to see any difference.

3
| username: redgame | Original post link

JOB_TYPE as txn-merge indicates that TiDB is performing batch commit operations on a large volume of transaction data to reduce the number of commit transactions and optimize index performance.

4
| username: 我是咖啡哥 | Original post link

Yes, this status is normal.

5
| username: 我是咖啡哥 | Original post link

Is it mentioned in any official documentation?

6
| username: system | Original post link

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