[jira] [Updated] (REEF-1527) Graceful shutdown of the RuntimeClock is not so graceful: unconditionally clears the event queue

["Sergiy Matusevych (JIRA)" <ji...@apache.org>]

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

Sergiy Matusevych updated REEF-1527:
------------------------------------
    Description: 
REEF {{RuntimeClock.close()}} method that is supposed to perform a graceful shutdown of the event loop, contains the following code:

{code:java}
this.schedule.clear();
this.schedule.add(new StopTime(findAcceptableStopTime()));
{code}

The problem is that {{findAcceptableStopTime()}} searches the schedule for the last client alarm - when the schedule has been cleared already.

We need to schedule StopTime event without clearing the schedule to allow graceful shutdown, but close the clock so no events will be scheduled after it.

  was:
REEF {{RuntimeClock.close()}} method that is supposed to perform a graceful shutdown of the event loop, contains the following code:

{code:java}
this.schedule.clear();
this.schedule.add(new StopTime(findAcceptableStopTime()));
{code}

The problem is that {{findAcceptableStopTime()}} searches the schedule for the last client alarm - when the schedule has been cleared already.

We need to schedule StopTime event without clearing the schedule to allow graceful shutdown, but close the clock so no events will be scheduled after it..


> Graceful shutdown of the RuntimeClock is not so graceful: unconditionally clears the event queue
> ------------------------------------------------------------------------------------------------
>
>                 Key: REEF-1527
>                 URL: https://issues.apache.org/jira/browse/REEF-1527
>             Project: REEF
>          Issue Type: Bug
>          Components: Wake
>            Reporter: Sergiy Matusevych
>            Assignee: Sergiy Matusevych
>              Labels: bug, events
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> REEF {{RuntimeClock.close()}} method that is supposed to perform a graceful shutdown of the event loop, contains the following code:
> {code:java}
> this.schedule.clear();
> this.schedule.add(new StopTime(findAcceptableStopTime()));
> {code}
> The problem is that {{findAcceptableStopTime()}} searches the schedule for the last client alarm - when the schedule has been cleared already.
> We need to schedule StopTime event without clearing the schedule to allow graceful shutdown, but close the clock so no events will be scheduled after it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)