This is an automated email from the ASF dual-hosted git repository.

xtsong pushed a commit to branch release-1.13
in repository https://gitbox.apache.org/repos/asf/flink.git


The following commit(s) were added to refs/heads/release-1.13 by this push:
     new 5e336cf  [FLINK-22335][runtime][config] Increase default resource wait 
timeout for the adaptive scheduler.
5e336cf is described below

commit 5e336cf0f7e79f197e8e4c61568fc9c3d183fa8f
Author: Xintong Song <[email protected]>
AuthorDate: Mon Apr 19 11:24:25 2021 +0800

    [FLINK-22335][runtime][config] Increase default resource wait timeout for 
the adaptive scheduler.
    
    This closes #15657
---
 docs/layouts/shortcodes/generated/all_jobmanager_section.html         | 4 ++--
 docs/layouts/shortcodes/generated/expert_scheduling_section.html      | 4 ++--
 docs/layouts/shortcodes/generated/job_manager_configuration.html      | 4 ++--
 .../main/java/org/apache/flink/configuration/JobManagerOptions.java   | 2 +-
 4 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/layouts/shortcodes/generated/all_jobmanager_section.html 
b/docs/layouts/shortcodes/generated/all_jobmanager_section.html
index 5d4666c..d542cab 100644
--- a/docs/layouts/shortcodes/generated/all_jobmanager_section.html
+++ b/docs/layouts/shortcodes/generated/all_jobmanager_section.html
@@ -16,13 +16,13 @@
         </tr>
         <tr>
             
<td><h5>jobmanager.adaptive-scheduler.resource-stabilization-timeout</h5></td>
-            <td style="word-wrap: break-word;">10 s</td>
+            <td style="word-wrap: break-word;">5 min</td>
             <td>Duration</td>
             <td>The resource stabilization timeout defines the time the 
JobManager will wait if fewer than the desired but sufficient resources are 
available. The timeout starts once sufficient resources for running the job are 
available. Once this timeout has passed, the job will start executing with the 
available resources.<br />If <code 
class="highlighter-rouge">scheduler-mode</code> is configured to <code 
class="highlighter-rouge">REACTIVE</code>, this configuration value will defaul 
[...]
         </tr>
         <tr>
             
<td><h5>jobmanager.adaptive-scheduler.resource-wait-timeout</h5></td>
-            <td style="word-wrap: break-word;">10 s</td>
+            <td style="word-wrap: break-word;">5 min</td>
             <td>Duration</td>
             <td>The maximum time the JobManager will wait to acquire all 
required resources after a job submission or restart. Once elapsed it will try 
to run the job with a lower parallelism, or fail if the minimum amount of 
resources could not be acquired.<br />Increasing this value will make the 
cluster more resilient against temporary resources shortages (e.g., there is 
more time for a failed TaskManager to be restarted).<br />Setting a negative 
duration will disable the resource tim [...]
         </tr>
diff --git a/docs/layouts/shortcodes/generated/expert_scheduling_section.html 
b/docs/layouts/shortcodes/generated/expert_scheduling_section.html
index 409ecb9..3e7807b 100644
--- a/docs/layouts/shortcodes/generated/expert_scheduling_section.html
+++ b/docs/layouts/shortcodes/generated/expert_scheduling_section.html
@@ -22,13 +22,13 @@
         </tr>
         <tr>
             
<td><h5>jobmanager.adaptive-scheduler.resource-stabilization-timeout</h5></td>
-            <td style="word-wrap: break-word;">10 s</td>
+            <td style="word-wrap: break-word;">5 min</td>
             <td>Duration</td>
             <td>The resource stabilization timeout defines the time the 
JobManager will wait if fewer than the desired but sufficient resources are 
available. The timeout starts once sufficient resources for running the job are 
available. Once this timeout has passed, the job will start executing with the 
available resources.<br />If <code 
class="highlighter-rouge">scheduler-mode</code> is configured to <code 
class="highlighter-rouge">REACTIVE</code>, this configuration value will defaul 
[...]
         </tr>
         <tr>
             
<td><h5>jobmanager.adaptive-scheduler.resource-wait-timeout</h5></td>
-            <td style="word-wrap: break-word;">10 s</td>
+            <td style="word-wrap: break-word;">5 min</td>
             <td>Duration</td>
             <td>The maximum time the JobManager will wait to acquire all 
required resources after a job submission or restart. Once elapsed it will try 
to run the job with a lower parallelism, or fail if the minimum amount of 
resources could not be acquired.<br />Increasing this value will make the 
cluster more resilient against temporary resources shortages (e.g., there is 
more time for a failed TaskManager to be restarted).<br />Setting a negative 
duration will disable the resource tim [...]
         </tr>
diff --git a/docs/layouts/shortcodes/generated/job_manager_configuration.html 
b/docs/layouts/shortcodes/generated/job_manager_configuration.html
index 2a82ba6..619e86e 100644
--- a/docs/layouts/shortcodes/generated/job_manager_configuration.html
+++ b/docs/layouts/shortcodes/generated/job_manager_configuration.html
@@ -16,13 +16,13 @@
         </tr>
         <tr>
             
<td><h5>jobmanager.adaptive-scheduler.resource-stabilization-timeout</h5></td>
-            <td style="word-wrap: break-word;">10 s</td>
+            <td style="word-wrap: break-word;">5 min</td>
             <td>Duration</td>
             <td>The resource stabilization timeout defines the time the 
JobManager will wait if fewer than the desired but sufficient resources are 
available. The timeout starts once sufficient resources for running the job are 
available. Once this timeout has passed, the job will start executing with the 
available resources.<br />If <code 
class="highlighter-rouge">scheduler-mode</code> is configured to <code 
class="highlighter-rouge">REACTIVE</code>, this configuration value will defaul 
[...]
         </tr>
         <tr>
             
<td><h5>jobmanager.adaptive-scheduler.resource-wait-timeout</h5></td>
-            <td style="word-wrap: break-word;">10 s</td>
+            <td style="word-wrap: break-word;">5 min</td>
             <td>Duration</td>
             <td>The maximum time the JobManager will wait to acquire all 
required resources after a job submission or restart. Once elapsed it will try 
to run the job with a lower parallelism, or fail if the minimum amount of 
resources could not be acquired.<br />Increasing this value will make the 
cluster more resilient against temporary resources shortages (e.g., there is 
more time for a failed TaskManager to be restarted).<br />Setting a negative 
duration will disable the resource tim [...]
         </tr>
diff --git 
a/flink-core/src/main/java/org/apache/flink/configuration/JobManagerOptions.java
 
b/flink-core/src/main/java/org/apache/flink/configuration/JobManagerOptions.java
index 2927d9f..4cb52e5 100644
--- 
a/flink-core/src/main/java/org/apache/flink/configuration/JobManagerOptions.java
+++ 
b/flink-core/src/main/java/org/apache/flink/configuration/JobManagerOptions.java
@@ -401,7 +401,7 @@ public class JobManagerOptions {
     public static final ConfigOption<Duration> RESOURCE_WAIT_TIMEOUT =
             key("jobmanager.adaptive-scheduler.resource-wait-timeout")
                     .durationType()
-                    .defaultValue(Duration.ofSeconds(10))
+                    .defaultValue(Duration.ofMinutes(5))
                     .withDescription(
                             Description.builder()
                                     .text(

Reply via email to