Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-3475

MapOutputBuffer allocates 4x as much space to record capacity as intended

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.17.0
    • Fix Version/s: 0.17.1
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      When setting up its accounting tables, MapTask.MapOutputBuffer calculates the size of each of its buffers as:

      Where #total_bytes is $io.sort.mb * 2^20 and #accounting_bytes is $io.sort.record.percent * #total_bytes
      kvbuffer: #total_bytes - #accounting_bytes
      kvoffsets: 1/4 of #accounting_bytes
      kvindices: 3/4 of #accounting_bytes
      

      kvoffsets and kvindices are ints, not bytes; the size of both arrays is incorrectly calculated.

        Attachments

        1. 3475-1.patch
          1 kB
          Chris Douglas
        2. 3475-2.patch
          1 kB
          Chris Douglas

          Issue Links

            Activity

              People

              • Assignee:
                chris.douglas Chris Douglas
                Reporter:
                chris.douglas Chris Douglas
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: