XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.8.0
    • Fix Version/s: 1.11.0
    • Component/s: None
    • Labels:
      None

      Description

      The memory limit cases for the spill-needed test seem inconsistent:

      For the test for in-memory sort:

          long currentlyAvailable =  popConfig.getMaxAllocation() - oAllocator.getAllocatedMemory();
      

      For reaching the memory limit:

      oAllocator.getAllocatedMemory() > .95 * oAllocator.getLimit()
      

      That is, one uses oAllocator.getLimit ("the current maximum limit this allocator imposes"), the other uses popConfig.getMaxAllocation ("The maximum memory this operator can allocate".)

        Attachments

          Activity

            People

            • Assignee:
              paul-rogers Paul Rogers
              Reporter:
              paul-rogers Paul Rogers
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: