Mailing-List: contact dev-help@reef.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@reef.apache.org
Date: Wed, 11 May 2016 20:17:12 +0000 (UTC)
From: "Mariia Mykhailova (JIRA)" <jira@apache.org>
To: dev@reef.apache.org
Message-ID: <JIRA.12967916.1462997793000.169391.1462997832966@Atlassian.JIRA>
In-Reply-To: <JIRA.12967916.1462997793000@Atlassian.JIRA>
References: <JIRA.12967916.1462997793000@Atlassian.JIRA> <JIRA.12967916.1462997793829@arcas>
Subject: [jira] [Created] (REEF-1388) Fix RunningTask to be sent for
 short-lived .NET tasks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 11 May 2016 20:17:14 -0000

Mariia Mykhailova created REEF-1388:
---------------------------------------

             Summary: Fix RunningTask to be sent for short-lived .NET tasks
                 Key: REEF-1388
                 URL: https://issues.apache.org/jira/browse/REEF-1388
             Project: REEF
          Issue Type: Bug
          Components: REEF.NET
            Reporter: Mariia Mykhailova
            Assignee: Mariia Mykhailova


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
(v6.3.4#6332)