commit | dd14f091050b9e8f22cff3627a8be686fd91350e | [log] [tgz] |
---|---|---|
author | Julia Wang <jwang98052@yahoo.com> | Tue Nov 29 18:34:38 2016 -0800 |
committer | Mariia Mykhailova <mariia@apache.org> | Fri Dec 02 13:59:23 2016 -0800 |
tree | ec0e3c1f519b2668f3d721dd76f843d63f4acdbe | |
parent | c0ddcc9c95b946abb346c1521eb3fc8fee1c22b6 [diff] |
[REEF-1679] Evaluator shouldn't go to recovery mode if there is no reconnect logic provided If there is no IDriverConnection bound, instead of throwing exception after a few quick retries, we will increase the retry number and finally exit the evaluator if it reaches max retry limit. If there is a IDriverConnection implemented, we will increase the max retry number since network glitch could happen for more than a few seconds. JIRA: [REEF-1679](https://issues.apache.org/jira/browse/REEF-1679) Pull request: This closes #1193
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 |