Current TSO Physical on PD Monitoring

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

Original topic: PD监控上的Current TSO Physcial

| username: chenhanneu

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Problem Phenomenon and Impact]
Can these two times on the PD monitoring be converted to each other?
What is the impact of manually adjusting the PD leader’s time forward and backward?
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachment: Screenshot/Log/Monitoring]
c99eae19df50df4813c11ffd01afcc3

| username: tidb菜鸟一只 | Original post link

| username: WalterWj | Original post link

PD distributes TSO with local clock and logical clock components. In theory, adjusting the server time shouldn’t be a big issue. However, it’s not recommended to do so.

| username: zhanggame1 | Original post link

TSO is calculated using time, which has a larger range than a timestamp and can be used.
BEGIN;
SELECT TIDB_PARSE_TSO(@@tidb_current_ts);
ROLLBACK;

| username: zhanggame1 | Original post link

Calculating time as TSO is also possible. Try this:

select REPLACE(unix_timestamp(current_timestamp(3)),'.','') << 18 as current_tso;
| username: redgame | Original post link

“Current TSO Physical” will be greater than “Current Time”

| username: system | Original post link

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