Backup reports "[pd] fetch pending tso requests error" [dc-location=global] [error="[PD:client:ErrClientGetTSO]context canceled: context canceled

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

Original topic: [br备份报"[pd] fetch pending tso requests error"] [dc-location=global] error="[PD:client:ErrClientGetTSO]context canceled: context canceled

| username: qhd2004

【TiDB Usage Environment】Production\Test Environment\POC
【TiDB Version】
tidb version is v5.4.1
tidb-toolkit-v5.4.1-linux-amd64/bin/br -V
Release Version: v5.4.1
【Encountered Problem】
/home/appadmin/tidb-toolkit-v5.2.2-linux-amd64/bin/br backup full --pd “${PDIP}:${PDPORT}” -s “s3://${miniobucket}/${miniodir}/${rq}” --s3.endpoint “$miniourl” --log-file ${backup_log}
No error occurred when using v5.2.2 version br to backup v5.4.1 version tidb cluster, the relevant logs are as follows:

/home/appadmin/tidb-toolkit-v5.4.1-linux-amd64/bin/br backup full --pd “${PDIP}:${PDPORT}” -s “s3://${miniobucket}/${miniodir}/${rq}” --s3.endpoint “$miniourl” --log-file ${backup_log}
However, when using v5.4.1 version br to backup v5.4.1 version tidb cluster, there was an error, but br was also successful, the relevant logs are as follows:

【Reproduction Path】What operations were performed to cause the problem
【Problem 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 one hour before and after the problem)

If the question is related to performance optimization or fault troubleshooting, please download the script and run it. Please select all and copy and paste the terminal output results for upload.

| username: TammyLi | Original post link

Can this issue be reproduced? It looks like the connection with PD was lost.

| username: qhd2004 | Original post link

It can be reproduced. Every time I use version v5.4.1 for BR backup, it is like this.

| username: xiaohetao | Original post link

Check out this post to see if it helps.

| username: xiaohetao | Original post link

Sorry, I can’t assist with that.

| username: qhd2004 | Original post link

Thank you!
In this article, the error in the log during the br backup is the same as mine. I suspect there is an issue or bug in version v5.4.1 of br. For now, I’ll revert to using v5.2.2.

| username: system | Original post link

This topic was automatically closed 1 minute after the last reply. No new replies are allowed.