[flink] branch release-1.13 updated: [FLINK-22819][yarn] Remove 'yarn.am.liveness-monitor.expiry-interval-ms' override for tests.

[trohrmann]

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

trohrmann 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 3708cc4  [FLINK-22819][yarn] Remove 
'yarn.am.liveness-monitor.expiry-interval-ms' override for tests.
3708cc4 is described below

commit 3708cc4cf9382f18e2f8e48b91d7c7dac74d607b
Author: David Moravek <d...@apache.org>
AuthorDate: Wed Jul 7 15:27:07 2021 +0200

    [FLINK-22819][yarn] Remove 'yarn.am.liveness-monitor.expiry-interval-ms' 
override for tests.
    
    This is an interval between AM container allocation and actually running RM 
Client inside this container,
    which can take longer in resource limited environment such as CI. If 
heartbeats between AM and RM don't
    work and a test relies on this, then it will fail a bit later because the 
default value is 5 minutes.
    
    This closes #16413.
---
 .../src/test/java/org/apache/flink/yarn/YarnTestBase.java             | 4 ----
 1 file changed, 4 deletions(-)

diff --git 
a/flink-yarn-tests/src/test/java/org/apache/flink/yarn/YarnTestBase.java 
b/flink-yarn-tests/src/test/java/org/apache/flink/yarn/YarnTestBase.java
index da334c9..b4dc3d3 100644
--- a/flink-yarn-tests/src/test/java/org/apache/flink/yarn/YarnTestBase.java
+++ b/flink-yarn-tests/src/test/java/org/apache/flink/yarn/YarnTestBase.java
@@ -217,12 +217,8 @@ public abstract class YarnTestBase extends TestLogger {
         YARN_CONFIGURATION.setInt(
                 YarnConfiguration.NM_VCORES, 666); // memory is overwritten in 
the MiniYARNCluster.
         // so we have to change the number of cores for testing.
-        YARN_CONFIGURATION.setInt(
-                YarnConfiguration.RM_AM_EXPIRY_INTERVAL_MS,
-                20000); // 20 seconds expiry (to ensure we properly heartbeat 
with YARN).
         YARN_CONFIGURATION.setFloat(
                 YarnConfiguration.NM_MAX_PER_DISK_UTILIZATION_PERCENTAGE, 
99.0F);
-
         YARN_CONFIGURATION.set(YarnConfiguration.YARN_APPLICATION_CLASSPATH, 
getYarnClasspath());
     }