reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mariia Mykhailova (JIRA)" <>
Subject [jira] [Commented] (REEF-1388) Fix RunningTask to be sent for short-lived .NET tasks
Date Wed, 11 May 2016 23:33:12 GMT


Mariia Mykhailova commented on REEF-1388:

{{}} looks like we send it before {{}}

  public void run() {
    try {
      // Change state and inform the Driver

      LOG.log(Level.FINEST, "Informing registered EventHandler<TaskStart>.");
      this.currentStatus.setRunning();  <----- this sends RUNNING heartbeat

      // Call
      final byte[] result = this.runTask();

      // Inform the Driver about it

      LOG.log(Level.FINEST, "Informing registered EventHandler<TaskStop>.");

> Fix RunningTask to be sent for short-lived .NET tasks
> -----------------------------------------------------
>                 Key: REEF-1388
>                 URL:
>             Project: REEF
>          Issue Type: Bug
>          Components: REEF.NET
>            Reporter: Mariia Mykhailova
>            Assignee: Mariia Mykhailova
>              Labels: FT
> Currently our task start handling code works as follows:
> 1. Send INIT message to driver.
> 2. Start task.
> 3. Send status updates as periodic heartbeat with 4 seconds period; first RUNNING status
received by java code triggers RunningTask event.
> If the task completes fast enough, periodic heartbeat might not catch task in process
of execution, and thus driver will never receive RunningTask event. All our tests which rely
on RunningTask have tasks which either sleep for 5+ seconds or wait until a RunningTask handler
sends a message to the task, so they never uncover this issue. This seems to be a bad design.
We need to fix this (and probably also reduce amount of sleep in some tests in spirit of REEF-1203).

This message was sent by Atlassian JIRA

View raw message