You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Sergiy Matusevych (JIRA)" <ji...@apache.org> on 2016/10/18 23:38:58 UTC
[jira] [Updated] (REEF-1645) Assertion in RuntimeClock.stop() is
always true
[ https://issues.apache.org/jira/browse/REEF-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergiy Matusevych updated REEF-1645:
------------------------------------
Description:
{{RuntimeClock.stop()}} assertion for {{numClientAlarms}} is placed immediately *after* its assigment. It should be the other way around.
It would also be helpful to print the number of outstanding alarms to the log to debug clock idleness/shutdown issues.
was:
{{RuntimeClock.stop()}} assertion for {{numClientAlarms}} is placed immediately **after** its assigment. It should be the other way around.
It would also be helpful to print the number of outstanding alarms to the log to debug clock idleness/shutdown issues.
> Assertion in RuntimeClock.stop() is always true
> -----------------------------------------------
>
> Key: REEF-1645
> URL: https://issues.apache.org/jira/browse/REEF-1645
> Project: REEF
> Issue Type: Bug
> Components: REEF-Common
> Reporter: Sergiy Matusevych
> Assignee: Sergiy Matusevych
> Priority: Trivial
> Labels: assertion, clock
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> {{RuntimeClock.stop()}} assertion for {{numClientAlarms}} is placed immediately *after* its assigment. It should be the other way around.
> It would also be helpful to print the number of outstanding alarms to the log to debug clock idleness/shutdown issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)