Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/5297#discussion_r27698365
--- Diff: docs/running-on-yarn.md ---
@@ -196,6 +196,15 @@ Most of the configs are the same for Spark on YARN as
for other deployment modes
It should be no larger than the global number of max attempts in the
YARN configuration.
</td>
</tr>
+<tr>
+ <td><code>spark.yarn.submit.waitAppCompletion</code></td>
--- End diff --
Is the purpose of making this configurable to provide backward
compatibility? I wonder if the new behavior should just be the default; I can't
imagine someone actually going out of his/her way to set this to false
explicitly. On the other hand people may rely on the existing behavior to
detect when the application has finished. What do others think?
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
