Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Tue, 22 Sep 2015 19:30:04 +0000 (UTC)
From: "Deneche A. Hakim (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12895023.1442801980000.42591.1442950204930@Atlassian.JIRA>
In-Reply-To: <JIRA.12895023.1442801980000@Atlassian.JIRA>
References: <JIRA.12895023.1442801980000@Atlassian.JIRA>
 <JIRA.12895023.1442801980395@arcas>
Subject: [jira] [Assigned] (DRILL-3811) AtomicRemainder incorrectly accounts
 for transferred allocations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DRILL-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Deneche A. Hakim reassigned DRILL-3811:
---------------------------------------

    Assignee: Deneche A. Hakim  (was: Chris Westin)

> AtomicRemainder incorrectly accounts for transferred allocations
> ----------------------------------------------------------------
>
>                 Key: DRILL-3811
>                 URL: https://issues.apache.org/jira/browse/DRILL-3811
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Relational Operators
>            Reporter: Deneche A. Hakim
>            Assignee: Deneche A. Hakim
>             Fix For: 1.2.0
>
>         Attachments: DRILL-3811.1.patch.txt
>
>
> when an allocator takes ownership of a buffer, AtomicRemainder.forceGet(int) is called to account for the extra memory of the buffer, but when the allocator exceeds it's maximum allocated memory it accounts for it incorrectly. In the following code, {{availableShared.andAndGet(size)}} should actually receive {{-size}}:
> {code}
> public boolean forceGet(long size) {
>     if (get(size, this.applyFragmentLimit)) {
>       return true;
>     } else {
>       availableShared.addAndGet(size);
>       if (parent != null) {
>         parent.forceGet(size);
>       }
>       return false;
>     }
>   }
> {code}
> I was able to reproduce the issue in a simple unit test


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