reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shouheng Yi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1537) LogicalTimer can cause a race condition in RuntimeClock
Date Mon, 20 Mar 2017 21:57:41 GMT

    [ https://issues.apache.org/jira/browse/REEF-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933655#comment-15933655
] 

Shouheng Yi commented on REEF-1537:
-----------------------------------

Any updates on this issue? Currently {{RuntimeClockTest.testAlarmOrder()}} uses {{RealTimer}}.
Is it still an issue with LogicalTimer? Thanks!

> LogicalTimer can cause a race condition in RuntimeClock
> -------------------------------------------------------
>
>                 Key: REEF-1537
>                 URL: https://issues.apache.org/jira/browse/REEF-1537
>             Project: REEF
>          Issue Type: Bug
>          Components: REEF-Common
>            Reporter: Sergiy Matusevych
>            Assignee: Sergiy Matusevych
>            Priority: Minor
>              Labels: race-condition, test
>
> {{RuntimeClock}} has a concept of injectable timer, and in many unit tests, we use {{LogicalTimer}}
to speed up the operations. Unfortunately, {{RuntimeClock}} still depends on the system timer
internally: it uses {{Object.wait(time)}} calls in the event loop. That can cause race conditions
when using {{LogicalTimer}}, e.g. in unit test {{ClockTest.testAlarmOrder()}}
> The solution would be to move the {{.wait()}} functionality into the logical timer and
use that inside the {{RuntimeClock}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message