[
https://issues.apache.org/jira/browse/IMPALA-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510283#comment-16510283
]
Mostafa Mokhtar commented on IMPALA-7096:
-----------------------------------------
[~tarmstrong]
Attached OOM profile where most memory is consumed by the HDFS_SCAN_NODE and
very little memory is in the queues.
{code}
Query Status: Memory limit exceeded: Error occurred on backend
vb0228.foo:22000 by fragment d7448d78ac85ba6b:303b72420000000c
Memory left in process limit: 98.37 GB
Memory left in query limit: -371.21 KB
Query(d7448d78ac85ba6b:303b724200000000): memory limit exceeded. Limit=1.00 GB
Reservation=816.00 MB ReservationLimit=819.20 MB OtherMemory=208.36 MB
Total=1.00 GB Peak=1.00 GB
Fragment d7448d78ac85ba6b:303b72420000000c: Reservation=360.00 MB
OtherMemory=85.60 MB Total=445.60 MB Peak=445.60 MB
HDFS_SCAN_NODE (id=2): Reservation=360.00 MB OtherMemory=85.45 MB
Total=445.45 MB Peak=445.45 MB
Exprs: Total=4.00 KB Peak=4.00 KB
Queued Batches: Total=22.13 MB Peak=22.13 MB
KrpcDataStreamSender (dst_id=13): Total=17.72 KB Peak=17.72 KB
CodeGen: Total=1.68 KB Peak=679.50 KB
Fragment d7448d78ac85ba6b:303b724200000023: Reservation=96.00 MB
OtherMemory=43.09 MB Total=139.09 MB Peak=139.09 MB
HDFS_SCAN_NODE (id=6): Reservation=96.00 MB OtherMemory=42.93 MB
Total=138.93 MB Peak=138.93 MB
Exprs: Total=4.00 KB Peak=4.00 KB
Queued Batches: Total=26.10 MB Peak=26.10 MB
KrpcDataStreamSender (dst_id=16): Total=17.72 KB Peak=17.72 KB
CodeGen: Total=1.68 KB Peak=679.50 KB
Fragment d7448d78ac85ba6b:303b72420000003a: Reservation=360.00 MB
OtherMemory=79.67 MB Total=439.67 MB Peak=439.67 MB
HDFS_SCAN_NODE (id=10): Reservation=360.00 MB OtherMemory=79.52 MB
Total=439.52 MB Peak=439.52 MB
Exprs: Total=4.00 KB Peak=4.00 KB
Queued Batches: Total=22.20 MB Peak=22.20 MB
KrpcDataStreamSender (dst_id=19): Total=17.72 KB Peak=17.72 KB
CodeGen: Total=1.68 KB Peak=679.50 KB
{code}
> Confirm that IMPALA-4835 does not increase chance of OOM for scans of wide
> tables
> ---------------------------------------------------------------------------------
>
> Key: IMPALA-7096
> URL: https://issues.apache.org/jira/browse/IMPALA-7096
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.13.0, Impala 3.1.0
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Blocker
> Labels: resource-management
> Attachments: ScanConsumingMostMemory.txt
>
>
> IMPALA-7078 showed some cases where non-buffer memory could accumulate in the
> row batch queue and cause memory consumption problems.
> The decision for whether to spin up a scanner thread in IMPALA-4835
> implicitly assumes that buffer memory is the bulk of memory consumed by a
> scan, but there may be cases where that is not true and the previous
> heuristic would be more conservative about starting a scanner thread.
> We should investigate this further and figure out how to avoid it if there's
> an issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
