The Role of Owner When Executing DDL

Translated
1

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

Original topic: 执行DDL时的owner角色

| username: alfred

【TiDB Usage Environment】Production\Test Environment\POC
【TiDB Version】
【Encountered Issues】
【Reproduction Path】What operations were performed that led to the issue
【Issue Phenomenon and Impact】
【Attachments】

  • Relevant logs, configuration files, Grafana monitoring (https://metricstool.pingcap.com/)
  • TiUP Cluster Display information
  • TiUP Cluster Edit config information
  • TiDB-Overview monitoring
  • Corresponding module’s Grafana monitoring (if any, such as BR, TiDB-binlog, TiCDC, etc.)
  • Corresponding module logs (including logs from 1 hour before and after the issue)

When executing DDL, the owner role is adopted on a rotating tenure basis. If a certain TiDB Server has a high load, will it still be rotated to be the owner?

For questions related to performance optimization or troubleshooting, please download the script and run it. Please select all and copy-paste the terminal output results for upload.

2
| username: TiDBer_h9um7nOg | Original post link

It should be

3
| username: alfred | Original post link

It would be better to accept PD scheduling based on the load situation.

4
| username: forever | Original post link

The owner node is generated using Etcd’s election function to elect an owner node from multiple TiDB nodes. The owner has a term, and the owner actively maintains its term by renewing it. When the owner node crashes, other nodes can detect it through Etcd and elect a new owner. According to this introduction, the owner should not switch if there is no crash or restart.

5
| username: alfred | Original post link

“It might not be reasonable to say ‘the owner won’t switch as long as there’s no crash or restart.’”

6
| username: system | Original post link

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