ueshin commented on a change in pull request #23416: [SPARK-26463][CORE] Use
ConfigEntry for hardcoded configs for scheduler categories.
URL: https://github.com/apache/spark/pull/23416#discussion_r245564725
##########
File path: core/src/main/scala/org/apache/spark/internal/config/package.scala
##########
@@ -206,6 +212,23 @@ package object config {
ConfigBuilder("spark.dynamicAllocation.executorAllocationRatio")
.doubleConf.createWithDefault(1.0)
+ private[spark] val DYN_ALLOCATION_CACHED_EXECUTOR_IDLE_TIMEOUT =
+ ConfigBuilder("spark.dynamicAllocation.cachedExecutorIdleTimeout")
+ .timeConf(TimeUnit.SECONDS).createWithDefault(Integer.MAX_VALUE)
+
+ private[spark] val DYN_ALLOCATION_EXECUTOR_IDLE_TIMEOUT =
+ ConfigBuilder("spark.dynamicAllocation.executorIdleTimeout")
+ .timeConf(TimeUnit.SECONDS).createWithDefault(60)
+
+ private[spark] val DYN_ALLOCATION_SCHEDULER_BACKLOG_TIMEOUT =
+ ConfigBuilder("spark.dynamicAllocation.schedulerBacklogTimeout")
+ .timeConf(TimeUnit.SECONDS).createWithDefault(1)
+
+ private[spark] val DYN_ALLOCATION_SUSTAINED_SCHEDULER_BACKLOG_TIMEOUT =
+ ConfigBuilder("spark.dynamicAllocation.sustainedSchedulerBacklogTimeout")
+ .timeConf(TimeUnit.SECONDS)
+
.createWithDefault(DYN_ALLOCATION_SCHEDULER_BACKLOG_TIMEOUT.defaultValue.get)
Review comment:
`fallbackConf(DYN_ALLOCATION_SCHEDULER_BACKLOG_TIMEOUT)`? Otherwise seems
like the behavior will change in `ExecutorAllocationManager`.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
