You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 24, 2021. It is now read-only.
The 'timezone' item in the current configuration file can be used to determine systemTZ and system_time_zone at the first bootstrap stage(eg. start from zero) of a TiDB cluster. However, after the first bootstrap, those two variables become read-only and never change for a cluster, more detailed information can be referenced as follows:
So, end-users may try to change 'timezone' for an existing TiDB cluster, for example, when doing a rolling-upgrade operation, but found nothing changes: 'timezone' can be confusing and misleading.
For the reason above it's better to remove 'timezone' in TiDB-Ansible, which lead the end-users to the configurations with explicit semantic, like the 'time_zone' system parameter in TiDB.
The text was updated successfully, but these errors were encountered:
The 'timezone' item in the current configuration file can be used to determine
systemTZ
andsystem_time_zone
at the first bootstrap stage(eg. start from zero) of a TiDB cluster. However, after the first bootstrap, those two variables become read-only and never change for a cluster, more detailed information can be referenced as follows:system_time_zone
fromsystem_tz
tidb#13934So, end-users may try to change 'timezone' for an existing TiDB cluster, for example, when doing a rolling-upgrade operation, but found nothing changes: 'timezone' can be confusing and misleading.
For the reason above it's better to remove 'timezone' in TiDB-Ansible, which lead the end-users to the configurations with explicit semantic, like the 'time_zone' system parameter in TiDB.
The text was updated successfully, but these errors were encountered: