Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0.2-alpha, 0.23.5
    • Fix Version/s: 2.0.3-alpha, 0.23.6
    • Component/s: applicationmaster
    • Labels:
      None

      Description

      It is possible for a networking issue to happen where the RM thinks an AM has gone down and launches a replacement, but the previous AM is still up and running. If the previous AM does not need any more resources from the RM it could try to commit either tasks or jobs. This could cause lots of problems where the second AM finishes and tries to commit too. This could result in data corruption.

      1. MAPREDUCE-4832.patch
        42 kB
        Jason Lowe
      2. MAPREDUCE-4832.patch
        41 kB
        Jason Lowe

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Jason Lowe
              Reporter:
              Robert Joseph Evans
            • Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development