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
sctool and service API accept timezone flag, which, according to the docs [1][2][3], specifies the timezone of cron and window flags.
--timezone
Timezone of –cron and –window flag values. The default value is taken from this system, namely ‘TZ’ envvar or ‘/etc/localtime’ file.
Default value: UTC
However, cron also accepts the extended syntax allowing for specifying TZ=<timezone> and CRON_TZ=<timezone>. It's undocumented in scylla-manager task docs, and it's not clear what the outcome of using it is, especially when used in tandem with timezone.
For instance, it's not clear what the difference between the following would be, or what behaviour should be expected:
I'd expect this to either be documented, or the additional syntax to be explicitly forbidden.
For reference, Kubernetes ran into a similar issue with CronJob [4], and the docs now specify that the extended syntax is not officially supported, and using the syntax results in a validation error in newer releases.
We must extend the documentation and explain what are the timezones that can be defined in task responsible for.
We must explain that cron specification allows to include the timezone.
We must understand how definining/not defining the timzeone in CRON impacts the scheduled task execution.
There is a timezone available for the manager overall (must be checked what is it about).
And the third timezone defines task.
So 3 timezones, per CRON, per task, per manager.
The goal of this task is to understand their meaning and impact + document them.
sctool and service API accept
timezone
flag, which, according to the docs [1][2][3], specifies the timezone ofcron
andwindow
flags.However,
cron
also accepts the extended syntax allowing for specifyingTZ=<timezone>
andCRON_TZ=<timezone>
. It's undocumented in scylla-manager task docs, and it's not clear what the outcome of using it is, especially when used in tandem withtimezone
.For instance, it's not clear what the difference between the following would be, or what behaviour should be expected:
I'd expect this to either be documented, or the additional syntax to be explicitly forbidden.
For reference, Kubernetes ran into a similar issue with CronJob [4], and the docs now specify that the extended syntax is not officially supported, and using the syntax results in a validation error in newer releases.
[1] - https://manager.docs.scylladb.com/stable/sctool/repair.html#timezone
[2] - https://manager.docs.scylladb.com/stable/sctool/backup.html#timezone
[3] - https://manager.docs.scylladb.com/stable/sctool/restore.html#timezone
[4] - https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#unsupported-timezone-specification
The text was updated successfully, but these errors were encountered: