[ 
https://issues.apache.org/jira/browse/DRILL-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466568#comment-16466568
 ] 

ASF GitHub Bot commented on DRILL-6348:
---------------------------------------

sachouche commented on issue #1237: DRILL-6348: Fixed code so that Unordered 
Receiver reports its memory …
URL: https://github.com/apache/drill/pull/1237#issuecomment-387229629
 
 
   Met with @parthchandra  and  @vrozov to discuss a more comprehensive fix:
   
   **Agreement**
   It was agreed that received batches should be owned by the associated 
receiver (not the fragment).
   This association is done at the framework level (Data Collector) so that the 
receiver doesn't have to perform any extra processing (such as explicit 
draining); this is to ensure that no side effect will occur (e.g., 
acknowledgment logic since it is sensitive to operator record consumption)
   
   **Fix**
   - Modified the Unordered & Merge receivers to register their buffer 
allocators with the associated Data Collector
   - The IncomingBuffers class now uses the operator's buffer allocator instead 
of the fragment allocator

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Unordered Receiver does not report its memory usage
> ---------------------------------------------------
>
>                 Key: DRILL-6348
>                 URL: https://issues.apache.org/jira/browse/DRILL-6348
>             Project: Apache Drill
>          Issue Type: Task
>          Components: Execution - Flow
>            Reporter: salim achouche
>            Assignee: salim achouche
>            Priority: Major
>             Fix For: 1.14.0
>
>
> The Drill Profile functionality doesn't show any memory usage for the 
> Unordered Receiver operator. This is problematic when analyzing OOM 
> conditions since we cannot account for all of a query memory usage. This Jira 
> is to fix memory reporting for the Unordered Receiver operator.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to