This is an automated email from the ASF dual-hosted git repository.
dongjoon pushed a commit to branch branch-2.4
in repository https://gitbox.apache.org/repos/asf/spark.git
The following commit(s) were added to refs/heads/branch-2.4 by this push:
new f1f6fc3 [MINOR][DOCS] Fix typos at ExecutorAllocationManager.scala
f1f6fc3 is described below
commit f1f6fc3ac3a48850530a36e19ad470902b037715
Author: JoeyValentine <[email protected]>
AuthorDate: Sat Aug 8 12:36:07 2020 -0700
[MINOR][DOCS] Fix typos at ExecutorAllocationManager.scala
### What changes were proposed in this pull request?
This PR fixes some typos in
<code>core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala</code>
file.
### Why are the changes needed?
<code>spark.dynamicAllocation.sustainedSchedulerBacklogTimeout</code> (N)
is used only after the
<code>spark.dynamicAllocation.schedulerBacklogTimeout</code> (M) is exceeded.
### Does this PR introduce _any_ user-facing change?
No.
### How was this patch tested?
No test needed.
Closes #29351 from JoeyValentine/master.
Authored-by: JoeyValentine <[email protected]>
Signed-off-by: Dongjoon Hyun <[email protected]>
(cherry picked from commit dc3fac81848f557e3dac3f35686af325a18d0291)
Signed-off-by: Dongjoon Hyun <[email protected]>
---
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala
b/core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala
index 36819aa..39f1cb6 100644
--- a/core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala
+++ b/core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala
@@ -44,8 +44,8 @@ import org.apache.spark.util.{Clock, SystemClock,
ThreadUtils, Utils}
* executors that could run all current running and pending tasks at once.
*
* Increasing the target number of executors happens in response to backlogged
tasks waiting to be
- * scheduled. If the scheduler queue is not drained in N seconds, then new
executors are added. If
- * the queue persists for another M seconds, then more executors are added and
so on. The number
+ * scheduled. If the scheduler queue is not drained in M seconds, then new
executors are added. If
+ * the queue persists for another N seconds, then more executors are added and
so on. The number
* added in each round increases exponentially from the previous round until
an upper bound has been
* reached. The upper bound is based both on a configured property and on the
current number of
* running and pending tasks, as described above.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
