Mailing-List: contact dev-help@reef.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@reef.apache.org
Date: Wed, 20 Jul 2016 17:45:20 +0000 (UTC)
From: "Markus Weimer (JIRA)" <jira@apache.org>
To: dev@reef.apache.org
Message-ID: <JIRA.12986047.1467342605000.85545.1469036720644@Atlassian.JIRA>
In-Reply-To: <JIRA.12986047.1467342605000@Atlassian.JIRA>
References: <JIRA.12986047.1467342605000@Atlassian.JIRA> <JIRA.12986047.1467342605481@arcas>
Subject: [jira] [Commented] (REEF-1480) Increase the retry count for task
 registration to high value
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 20 Jul 2016 17:45:22 -0000


    [ https://issues.apache.org/jira/browse/REEF-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386272#comment-15386272 ] 

Markus Weimer commented on REEF-1480:
-------------------------------------

+1

We should also consider making much of this code {{async}} to remove the needless waits.

> Increase the retry count for task registration to high value
> ------------------------------------------------------------
>
>                 Key: REEF-1480
>                 URL: https://issues.apache.org/jira/browse/REEF-1480
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF.NET
>         Environment: C#
>            Reporter: Dhruv Mahajan
>
> Currently, the default retry count in Group communication to wait for registration is set so that error is thrown after around 4 minutes. For IMRU tasks, if data downloading takes a lot of time error gets thrown. In general this can be the issue for any other application also since it is too lower level parameter to expose via application interfaces, for example {{IMRUJobDefinition}}. Like hadoop MapReduce, we can take a configuration file and then read these parameters from over there. For now, we would like to set the default to a very high value.


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