[
https://issues.apache.org/jira/browse/DRILL-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16455681#comment-16455681
]
ASF GitHub Bot commented on DRILL-6348:
---------------------------------------
Github user sachouche commented on the issue:
https://github.com/apache/drill/pull/1237
@vrozov, your observation is valid, we need more JIRAs to fix the reporting
problem
**Current Fix**
- At this time, the UnorderedReceiver didn't account for any consumed memory
- This fix, taxes the operator only when it consumes buffers
**Potential Enhancements**
Solution I
- Create a new fragment child Allocator which will own the received (not
yet consumed) batches
- Improve the UI to report this allocator size
- This solution is simple and complementary to the current work
Solution II
- Have the receiver operator drain the batch queue
- Essentially, the receiver will have a private queue from where to consume
batches
- I personally don't like this solution as it prevents us from improving
the Drill network protocol
- Draining the batches for the sake of reporting will make it harder for
the network layer to prefetch batches in an optimal manner; the queue size
should be an indicator on how many pending batches there are.
> 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)
