Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-4725

[Umbrella] Auto-­restart of containers

    XMLWordPrintableJSON

    Details

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

      Description

      See overview doc at YARN-4692, copying the sub-section to track all related efforts.

      Today, when a container (process­-tree) dies, NodeManager assumes that the container’s allocation is also expired, and reports accordingly to the ResourceManager which then releases the allocation. For service containers, this is undesirable in many cases. Long running containers may exit for various reasons, crash and need to restart but forcing them to go through the complete scheduling cycle, resource localization etc is both unnecessary and expensive. (​Task) ​For services it will be good to have NodeManagers automatically restart containers. This looks a lot like inittab / daemon­tools at the system level.

      We will need to enable app­-specific policies (very similar to the handling of AM restarts at YARN level) for restarting containers automatically but limit such restarts if a container dies too often in a short interval of time.

      YARN-3998 is an existing ticket that looks at some if not all of this functionality.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                vinodkv Vinod Kumar Vavilapalli
              • Votes:
                0 Vote for this issue
                Watchers:
                16 Start watching this issue

                Dates

                • Created:
                  Updated: