You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@reef.apache.org by "Mariia Mykhailova (JIRA)" <ji...@apache.org> on 2016/12/05 21:35:59 UTC

[jira] [Resolved] (REEF-1682) Update TCP Connection config values for IMRU example and test

     [ https://issues.apache.org/jira/browse/REEF-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mariia Mykhailova resolved REEF-1682.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.16

Resolved via [PR 1197|https://github.com/apache/reef/pull/1197]

> Update TCP Connection config values for IMRU example and test
> -------------------------------------------------------------
>
>                 Key: REEF-1682
>                 URL: https://issues.apache.org/jira/browse/REEF-1682
>             Project: REEF
>          Issue Type: Test
>            Reporter: Julia
>            Assignee: Julia
>             Fix For: 0.16
>
>
> Recent stress testing for IMRU FT shows when there are hundreds of hundreds nodes with many failed and re-requested elevators, the default Tcp connection retry time is not longer enough for evaluators to connect to driver, as driver might be very busy to handle a long event queue and each event handler is locked in IMRU driver. 
> We need to set proper configuration values for IMRU example which is used for running stress testing.
> In some of the IMRU tests, this configuration data is set through task function config that is incorrect. It should be set through configuration provider to make it work. 



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