[jira] [Updated] (DRILL-5020) ExternalSortBatch has inconsistent notions of the memory limit
[ https://issues.apache.org/jira/browse/DRILL-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5020: --- Fix Version/s: (was: 1.10.0) 1.11.0 > ExternalSortBatch has inconsistent notions of the memory limit > -- > > Key: DRILL-5020 > URL: https://issues.apache.org/jira/browse/DRILL-5020 > Project: Apache Drill > Issue Type: Sub-task >Affects Versions: 1.8.0 >Reporter: Paul Rogers >Assignee: Paul Rogers >Priority: Minor > Fix For: 1.11.0 > > > 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.15#6346)
[jira] [Updated] (DRILL-5020) ExternalSortBatch has inconsistent notions of the memory limit
[ https://issues.apache.org/jira/browse/DRILL-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5020: --- Fix Version/s: 1.10.0 > ExternalSortBatch has inconsistent notions of the memory limit > -- > > Key: DRILL-5020 > URL: https://issues.apache.org/jira/browse/DRILL-5020 > Project: Apache Drill > Issue Type: Sub-task >Affects Versions: 1.8.0 >Reporter: Paul Rogers >Assignee: Paul Rogers >Priority: Minor > Fix For: 1.10.0 > > > 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.15#6346)
[jira] [Updated] (DRILL-5020) ExternalSortBatch has inconsistent notions of the memory limit
[ https://issues.apache.org/jira/browse/DRILL-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5020: --- Issue Type: Sub-task (was: Bug) Parent: DRILL-5080 > ExternalSortBatch has inconsistent notions of the memory limit > -- > > Key: DRILL-5020 > URL: https://issues.apache.org/jira/browse/DRILL-5020 > Project: Apache Drill > Issue Type: Sub-task >Affects Versions: 1.8.0 >Reporter: Paul Rogers >Assignee: 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)
[jira] [Updated] (DRILL-5020) ExternalSortBatch has inconsistent notions of the memory limit
[ https://issues.apache.org/jira/browse/DRILL-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5020: --- Summary: ExternalSortBatch has inconsistent notions of the memory limit (was: ExernalSortBatch has inconsistent notions of the memory limit) > ExternalSortBatch 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 >Assignee: 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)