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

Posted to dev@reef.apache.org by "Julia (JIRA)" <ji...@apache.org> on 2016/12/02 00:24:59 UTC

[jira] [Updated] (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 ]

Julia updated REEF-1682:
------------------------
    Description: 
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. 


  was:
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, and for functional test. 


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