[
https://issues.apache.org/jira/browse/HDDS-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932389#comment-17932389
]
Tsz-wo Sze edited comment on HDDS-12459 at 3/4/25 5:46 PM:
-----------------------------------------------------------
[~chiacyu], thanks for pointing out HDDS-12060. They are essentially the same
problem. However,
- HDDS-12060 focuses on System.currentTimeMillis(), and
- this focuses on java.time.Clock.
We probably should fix them in two JIRAs since it will involve different areas.
was (Author: szetszwo):
[~chiacyu], thanks for pointing out HDDS-12060. They are essentially the same
problem. However,
- HDDS-12060 focuses on System.currentTimeMillis(), and
- this focuses on java.time.Clock.
We probably should fix them in one or two JIRAs since it will involve different
areas.
> System clock should not be used for measuring time duration
> -----------------------------------------------------------
>
> Key: HDDS-12459
> URL: https://issues.apache.org/jira/browse/HDDS-12459
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Tsz-wo Sze
> Priority: Major
>
> java.time.Clock (system(ZoneId) / systemDefaultZone() / systemUTC()) uses
> System.currentTimeMillis(). As described in HADOOP-15901, this could result
> in undesired results when system clock's time changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
