[
https://issues.apache.org/jira/browse/IMPALA-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611009#comment-16611009
]
Tim Armstrong commented on IMPALA-5463:
---------------------------------------
[~tozka] those stack traces are associated with the embedded JVM doing GC. You
can probably avoid that by increasing the size of the embedded JVM. You can
pass flags into the embedded JVM by setting JAVA_TOOL_OPTIONS in the
environment of the impala daemon, e.g.
{code}
JAVA_TOOL_OPTIONS="-Xmx20g"
{code}
The metric jvm.heap.max-usage-bytes (visible on on the impalad debug page) is
one way to see the current heap size.
> OOM during clone() causes crash in libjvm.so!java_start()
> ---------------------------------------------------------
>
> Key: IMPALA-5463
> URL: https://issues.apache.org/jira/browse/IMPALA-5463
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.8.0
> Reporter: Lars Volker
> Priority: Critical
> Attachments: stack-trace-threads-high-cpu.txt
>
>
> Running out of memory seems to cause a crash in libjvm.so!java_start() right
> after calling clone(). Here is the stack trace of the crashing thread from a
> minidump.
> {noformat}
> 0 libjvm.so!PSParallelCompact::MarkAndPushClosure::do_oop(oopDesc**) + 0x86
> 1 libjvm.so!OopMapSet::all_do(frame const*, RegisterMap const*,
> OopClosure*, void (*)(oopDesc**, oopDesc**), OopClosure*) + 0x2fb
> 2 libjvm.so!frame::oops_do_internal(OopClosure*, CLDClosure*,
> CodeBlobClosure*, RegisterMap*, bool) + 0xa2
> 3 libjvm.so!JavaThread::oops_do(OopClosure*, CLDClosure*, CodeBlobClosure*)
> + 0x161
> 4 libjvm.so!ThreadRootsMarkingTask::do_it(GCTaskManager*, unsigned int) +
> 0x106
> 5 libjvm.so!GCTaskThread::run() + 0x12f
> 6 libjvm.so!java_start(Thread*) + 0x108
> 7 libpthread-2.12.so!start_thread + 0xd1
> 8 libc-2.12.so!clone + 0x6d
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
