[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
5 files changed
tree: ec0e3c1f519b2668f3d721dd76f843d63f4acdbe
  1. bin/
  2. dev/
  3. lang/
  4. website/
  5. .gitattributes
  6. .gitignore
  7. .travis.yml
  8. appveyor.yml
  9. Doxyfile
  10. HEADER
  11. LICENSE
  12. NOTICE
  13. pom.xml
  14. README.md
README.md

Apache REEF™

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.

Online Documentation

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.

Build Status

ComponentOSStatus
REEF JavaUbuntuBuild Status
REEF.NETWindowsBuild status

Building REEF

Java.NET
Build & run unit testsjava\BUILD.mdcs\BUILD.md

Releases

downloads NuGet package

License

Apache 2.0