You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Dhruv Mahajan (JIRA)" <ji...@apache.org> on 2016/03/29 01:37:25 UTC
[jira] [Commented] (REEF-1292) Link and StreamingLink classes
should have retry logic for setting up remote connection
[ https://issues.apache.org/jira/browse/REEF-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215093#comment-15215093 ]
Dhruv Mahajan commented on REEF-1292:
-------------------------------------
I will try to retry some n times with a sleep of p milli secs. each retry. n and p will be configurable parameters with default values of 20 and 1000 respectively.
> Link and StreamingLink classes should have retry logic for setting up remote connection
> ---------------------------------------------------------------------------------------
>
> Key: REEF-1292
> URL: https://issues.apache.org/jira/browse/REEF-1292
> Project: REEF
> Issue Type: Improvement
> Components: Wake.NET
> Environment: C#
> Reporter: Dhruv Mahajan
> Assignee: Dhruv Mahajan
>
> Currently {{Org.Apache.REEF.Wake.Remote.Impl.Link}} and {{Org.Apache.REEF.Wake.Remote.Impl.StreamingLink}} try only once to establish connection to remote endpoint. However, if remote server is very busy or loaded, it might reject the connection. This can happen for example, when we ask for say 1000 evaluators and NameClient tries to open connection with NameServer which is overwhelmed because of huge traffic.
> The aim of JIRA is to introduce this re-try logic
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)