[jira] [Created] (MAPREDUCE-6659) Mapreduce App master waits long to kill containers on lost nodes.

["Laxman (JIRA)" <ji...@apache.org>]

Laxman created MAPREDUCE-6659:
---------------------------------

             Summary: Mapreduce App master waits long to kill containers on lost nodes.
                 Key: MAPREDUCE-6659
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6659
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: mr-am
    Affects Versions: 2.6.0
            Reporter: Laxman


MR Application master waits for very long time to cleanup and relaunch the tasks on lost nodes. Wait time is actually 2.5 hours (ipc.client.connect.max.retries * ipc.client.connect.max.retries.on.timeouts * ipc.client.connect.timeout = 10 * 45 * 20 = 9000 seconds = 2.5 hours)

Some similar issue related in RM-AM rpc protocol is fixed in YARN-3809.
As fixed in YARN-3809, we may need to introduce new configurations to control this RPC retry behavior.

Also, I feel this total retry time should honor and capped maximum to global task time out (mapreduce.task.timeout = 600000 default)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)