impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Taras Bobrovytsky (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IMPALA-5246) Queries failing with "Process: memory limit exceeded" during ASAN builds
Date Thu, 18 May 2017 19:52:04 GMT

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

Taras Bobrovytsky resolved IMPALA-5246.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.9.0

{code}
commit b73c445eba48a4637c5642fa1866e237617a322d
Author: Taras Bobrovytsky <tbobrovytsky@cloudera.com>
Date:   Thu May 11 13:54:13 2017 -0700

    IMPALA-5246: Verify that a UDF test completely finishes before moving on
    
    A memory intensive UDF test takes a while to completely finish and for
    the memory in Impala to be completely freed. This caused a problem in
    ASAN builds (and potentially in normal builds) because we would start
    the next test right away, before the memory is freed.
    
    We fix the issue by checking that all fragments finish executing before
    starting the next test.
    
    Testing:
    - Ran a private ASAN build which passed.
{code}

> Queries failing with "Process: memory limit exceeded" during ASAN builds
> ------------------------------------------------------------------------
>
>                 Key: IMPALA-5246
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5246
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.9.0
>            Reporter: Michael Ho
>            Assignee: Taras Bobrovytsky
>            Priority: Blocker
>              Labels: broken-build
>             Fix For: Impala 2.9.0
>
>
> {noformat}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00007f4eef4dbc33, pid=1812, tid=139979017721600
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_75-b13) (build 1.7.0_75-b13)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode linux-amd64 compressed
oops)
> # Problematic frame:
> # C  [libTestUdfs.1812.4.so+0x5c33]  MemTestClose(impala_udf::FunctionContext*, impala_udf::FunctionContext::FunctionStateScope)+0x33
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try
"ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # /data/jenkins/workspace/impala-umbrella-build-and-test/repos/hadoop-lzo/hs_err_pid1812.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://bugreport.sun.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> {noformat}
> Still trying to find the core file. Will provide backtrace if I can find it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message