Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-6659

Mapreduce App master waits long to kill containers on lost nodes.

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.6.0
    • Fix Version/s: None
    • Component/s: mr-am
    • Labels:
      None

      Description

      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)

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                nfraison.criteo Nicolas Fraison
                Reporter:
                lakshman Laxman
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated: