[
https://issues.apache.org/jira/browse/HDDS-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen O'Donnell resolved HDDS-7692.
-------------------------------------
Fix Version/s: 1.4.0
Resolution: Fixed
> Remove usage of MonotonicClock and use default system clock instead
> -------------------------------------------------------------------
>
> Key: HDDS-7692
> URL: https://issues.apache.org/jira/browse/HDDS-7692
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Stephen O'Donnell
> Assignee: Siddhant Sangwan
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> Similar to HDDS-7463, we are seeing that commands sent from SCM to the
> datanodes are being expired when they should not be. This is because we are
> getting the command deadline from MonotonicClock and then comparing that with
> the current time, also gotten from MonotonicClock on the datanodes.
> As we discovered in HDDS-7463, the "Time" monotonic clock uses is not system
> time, but some arbitrary reference point in the JVM. We cannot use the time
> from monotonic clock to compare times across JVM restarts, or in different
> JVMs.
> For that reason, I believe it would be safer to replace any usages of
> Monotonic clock with java.util.SystemClock.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
