| commit | 977965c239ec59888c0dae5309d598f00848824c | [log] [tgz] |
|---|---|---|
| author | Julia Wang <jwang98052@yahoo.com> | Thu Dec 01 16:27:59 2016 -0800 |
| committer | Mariia Mykhailova <mariia@apache.org> | Mon Dec 05 13:30:34 2016 -0800 |
| tree | 70480421cdb1a1b27a62f118f59f14601a0fb935 | |
| parent | 0d78bf8220a012c5d1b83db930ed431cfd521572 [diff] |
[REEF-1682] Update TCP connection config values for IMRU example and test Recent stress testing for IMRU FT shows when there are hundreds of nodes with many failed and re-requested evaluators, the default TCP connection retry time is not long enough for evaluators to connect to driver, as driver might be busy handling 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 is set via task function config, which has no effect. It should be set through configuration provider to work. This change sets TCP connection configuration values for IMRU example and fixes this setting in functional tests. JIRA: [REEF-1682](https://issues.apache.org/jira/browse/REEF-1682) Pull request: This closes #1197
Apache REEF™ (Retainable Evaluator Execution Framework) is a library for developing portable applications for cluster resource managers such as Apache Hadoop YARN or Apache Mesos. For example, Microsoft Azure Stream Analytics is built on REEF and Hadoop.
Detailed information on REEF can be found in the following places:
The developer mailing list is the best way to reach REEF‘s developers when the above aren’t sufficient.
| Component | OS | Status |
|---|---|---|
| REEF Java | Ubuntu |  |
| REEF.NET | Windows |
| Java | .NET | |
|---|---|---|
| Build & run unit tests | java\BUILD.md | cs\BUILD.md |
