[jira] [Created] (DRILL-5020) ExernalSortBatch has inconsistent notions of the memory limit

[Paul Rogers (JIRA)]

Paul Rogers created DRILL-5020:
----------------------------------

             Summary: ExernalSortBatch has inconsistent notions of the memory 
limit
                 Key: DRILL-5020
                 URL: https://issues.apache.org/jira/browse/DRILL-5020
             Project: Apache Drill
          Issue Type: Bug
    Affects Versions: 1.8.0
            Reporter: Paul Rogers
            Priority: Minor


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

For the test for in-memory sort:
{code}
    long currentlyAvailable =  popConfig.getMaxAllocation() - 
oAllocator.getAllocatedMemory();
{code}

For reaching the memory limit:
{code}
oAllocator.getAllocatedMemory() > .95 * oAllocator.getLimit()
{code}

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".)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)