reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anupam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1292) Link and StreamingLink classes should have retry logic for setting up remote connection
Date Tue, 29 Mar 2016 06:22:25 GMT

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

Anupam commented on REEF-1292:
------------------------------

Please take a look at classes in {Microsoft.Practices.TransientFaultHandling} and see if you
can use it. It is already used in O.A.R.IO and O.A.R.Client. One example is {Org.Apache.REEF.Client.YARN.RestClient.HttpClientRetryHandler}

> 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)

Mime
View raw message