reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergiy Matusevych (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (REEF-1645) Assertion in RuntimeClock.stop() is always true
Date Wed, 19 Oct 2016 00:15:58 GMT

     [ https://issues.apache.org/jira/browse/REEF-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sergiy Matusevych updated REEF-1645:
------------------------------------
    Labels: assertion clock logging  (was: assertion clock)

> 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, logging
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In {{RuntimeClock.stop()}}, the 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)

Mime
View raw message