Removing config for liveness check and making it default

Author: Ashutosh Gupta

hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapred/TaskAttemptListenerImpl.java

@@ -410,10 +410,7 @@ public AMFeedback statusUpdate(TaskAttemptID taskAttemptID,
         LOG.debug("Ping from " + taskAttemptID.toString());
       }
       // Consider ping from the tasks for liveliness check
-      if (getConfig().getBoolean(MRJobConfig.MR_TASK_ENABLE_PING_FOR_LIVELINESS_CHECK,
-          MRJobConfig.DEFAULT_MR_TASK_ENABLE_PING_FOR_LIVELINESS_CHECK)) {
-        taskHeartbeatHandler.progressing(yarnAttemptID);
-      }
+      taskHeartbeatHandler.progressing(yarnAttemptID);
       return feedback;
     }
 

hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/MRJobConfig.java

@@ -919,12 +919,6 @@ public interface MRJobConfig {
     MR_AM_PREFIX + "scheduler.heartbeat.interval-ms";
   public static final int DEFAULT_MR_AM_TO_RM_HEARTBEAT_INTERVAL_MS = 1000;
 
-  /** Whether to consider ping from tasks in liveliness check. */
-  String MR_TASK_ENABLE_PING_FOR_LIVELINESS_CHECK =
-      "mapreduce.task.enable.ping-for-liveliness-check";
-  boolean DEFAULT_MR_TASK_ENABLE_PING_FOR_LIVELINESS_CHECK
-      = true;
-
   /**
    * If contact with RM is lost, the AM will wait MR_AM_TO_RM_WAIT_INTERVAL_MS
    * milliseconds before aborting. During this interval, AM will still try

hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/mapred-default.xml

@@ -286,13 +286,6 @@
   </description>
 </property>
 
-<property>
-  <name>mapreduce.task.enable.ping-for-liveliness-check</name>
-  <value>true</value>
-  <description>Whether to consider ping from tasks in liveliness check.
-  </description>
-</property>
-
 <property>
   <name>mapreduce.map.memory.mb</name>
   <value>-1</value>