GitHub user jpgbus opened a pull request:
https://github.com/apache/zeppelin/pull/1993
[ZEPPELIN-1700] Update docs for ZEPPELIN_INTERPRETER_CONNECT_TIMEOUT
### What is this PR for?
Update docs to let devs know about
[ZEPPELIN_INTERPRETER_CONNECT_TIMEOUT](https://github.com/apache/zeppelin/blob/5bb38c89ae67f95858547f73d0e833ef91b3d6ee/zeppelin-zengine/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java#L576)
Some use cases are such that this value would need to be quite a bit
higher, e.g., exceed the time required to create the spark executors in a mesos
cluster. Developers may not know about this var until after they see the error
[ZEPPELIN-1700].
### What type of PR is it?
Documentation
### Todos
* [ ] - Review and merge
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1700
### How should this be tested?
Review that the documented values reflect code reality
https://github.com/apache/zeppelin/blob/5bb38c89ae67f95858547f73d0e833ef91b3d6ee/zeppelin-zengine/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java#L576
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? No.
* Is there breaking changes for older versions? No.
* Does this needs documentation? Yes; it is documentation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jpgbus/zeppelin patch-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1993.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1993
----
commit 22aad28ab179348bee69603e7a0f023e9f3fba2c
Author: jpgbus <[email protected]>
Date: 2017-02-08T14:32:57Z
This timeout should be included in docs
https://github.com/apache/zeppelin/blob/5bb38c89ae67f95858547f73d0e833ef91b3d6ee/zeppelin-zengine/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java#L576
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
