You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Joe McDonnell (JIRA)" <ji...@apache.org> on 2018/08/21 16:37:00 UTC
[jira] [Commented] (IMPALA-7465) Hit memory limit in
TestScanMemLimit.test_kudu_scan_mem_usage on ASAN build
[ https://issues.apache.org/jira/browse/IMPALA-7465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587696#comment-16587696 ]
Joe McDonnell commented on IMPALA-7465:
---------------------------------------
This happened again on the ASAN run.
[~tarmstrong@cloudera.com] , it looks like IMPALA-7096 introduced this, can you take a look and assign?
> Hit memory limit in TestScanMemLimit.test_kudu_scan_mem_usage on ASAN build
> ---------------------------------------------------------------------------
>
> Key: IMPALA-7465
> URL: https://issues.apache.org/jira/browse/IMPALA-7465
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 3.1.0
> Reporter: Joe McDonnell
> Priority: Critical
> Labels: broken-build
>
> An ASAN build encountered a failure in test_mem_usage_scaling.TestScanMemLimit.test_kudu_scan_mem_usage() due to hitting the memory limit:
> {noformat}
> E ImpalaBeeswaxException: ImpalaBeeswaxException:
> E Query aborted:Memory limit exceeded: Failed to allocate tuple buffer
> E KUDU_SCAN_NODE (id=0) could not allocate 110.00 KB without exceeding limit.
> E Error occurred on backend impala-ec2-centos74-m5-4xlarge-ondemand-0104.vpc.cloudera.com:22001 by fragment 8745b4d457dcf8ab:79a096ab00000003
> E Memory left in process limit: 11.53 GB
> E Memory left in query limit: 7.95 KB
> E Query(8745b4d457dcf8ab:79a096ab00000000): Limit=4.00 MB Reservation=0 ReservationLimit=0 OtherMemory=3.99 MB Total=3.99 MB Peak=3.99 MB
> E Fragment 8745b4d457dcf8ab:79a096ab00000003: Reservation=0 OtherMemory=3.99 MB Total=3.99 MB Peak=3.99 MB
> E SORT_NODE (id=1): Total=342.00 KB Peak=342.00 KB
> E KUDU_SCAN_NODE (id=0): Total=3.64 MB Peak=3.64 MB
> E Queued Batches: Total=3.63 MB Peak=3.63 MB
> E KrpcDataStreamSender (dst_id=2): Total=1.16 KB Peak=1.16 KB
> E CodeGen: Total=10.89 KB Peak=1.15 MB
> E
> E Memory limit exceeded: Failed to allocate tuple buffer
> E KUDU_SCAN_NODE (id=0) could not allocate 110.00 KB without exceeding limit.
> E Error occurred on backend impala-ec2-centos74-m5-4xlarge-ondemand-0104.vpc.cloudera.com:22001 by fragment 8745b4d457dcf8ab:79a096ab00000003
> E Memory left in process limit: 11.53 GB
> E Memory left in query limit: 7.95 KB
> E Query(8745b4d457dcf8ab:79a096ab00000000): Limit=4.00 MB Reservation=0 ReservationLimit=0 OtherMemory=3.99 MB Total=3.99 MB Peak=3.99 MB
> E Fragment 8745b4d457dcf8ab:79a096ab00000003: Reservation=0 OtherMemory=3.99 MB Total=3.99 MB Peak=3.99 MB
> E SORT_NODE (id=1): Total=342.00 KB Peak=342.00 KB
> E KUDU_SCAN_NODE (id=0): Total=3.64 MB Peak=3.64 MB
> E Queued Batches: Total=3.63 MB Peak=3.63 MB
> E KrpcDataStreamSender (dst_id=2): Total=1.16 KB Peak=1.16 KB
> E CodeGen: Total=10.89 KB Peak=1.15 MB{noformat}
> This test was introduced recently as part of IMPALA-7096.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org