[MAPREDUCE-7195] Mapreduce task timeout to zero could cause too many status update

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Bilwa S T
• Reporter: Bibin Chundatt
• Created: 21/Mar/19 07:30
• Updated: 21/Mar/19 08:51

Description

• mapreduce.task.timeout=0

Could create too many status update

  public static long getTaskProgressReportInterval(final Configuration conf) {
    long taskHeartbeatTimeOut = conf.getLong(
        MRJobConfig.TASK_TIMEOUT, MRJobConfig.DEFAULT_TASK_TIMEOUT_MILLIS);
    return conf.getLong(MRJobConfig.TASK_PROGRESS_REPORT_INTERVAL,
        (long) (TASK_REPORT_INTERVAL_TO_TIMEOUT_RATIO * taskHeartbeatTimeOut));
  }

mapreduce timeout=0 is used to disable timeout feature

Issue Links

• is caused by: MAPREDUCE-6740 Enforce mapreduce.task.timeout to be at least mapreduce.task.progress-report.interval