You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/07/16 14:43:00 UTC
[jira] [Updated] (HDDS-5456) Inject a Clock into Replication
Manager to allows timeouts to be tested
[ https://issues.apache.org/jira/browse/HDDS-5456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-5456:
---------------------------------
Labels: pull-request-available (was: )
> Inject a Clock into Replication Manager to allows timeouts to be tested
> -----------------------------------------------------------------------
>
> Key: HDDS-5456
> URL: https://issues.apache.org/jira/browse/HDDS-5456
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM
> Reporter: Stephen O'Donnell
> Assignee: Stephen O'Donnell
> Priority: Major
> Labels: pull-request-available
>
> Replication Manager current uses Time.monotonicNow() is a few places to check if a pending command should be timed out. Currently, this is difficult to test without adding sleeps in the test. We should inject a Clock object to use rather than making calls to SystemTime to allow tests more flexibility.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org