[
https://issues.apache.org/jira/browse/HBASE-18541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16125850#comment-16125850
]
Ted Yu commented on HBASE-18541:
--------------------------------
Installed openjdk-8-dbg
When loading core dump in gdb, I got:
{code}
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by
`/usr/src/hbase/hbase-native-client/buck-out/gen/core/retry-test
--gtest_color=n'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f1a735338d5 in ?? ()
[Current thread is 1 (Thread 0x7f1a8701d840 (LWP 12922))]
Installing openjdk unwinder
(gdb) bt
#0 0x00007f1a735338d5 in ()
#1 0x00007ffe78f88ba8 in ()
#2 0x00007f19e4d572c8 in ()
#3 0x0000000000000000 in ()
{code}
There was no detail for the seg fault.
> [C++] Segfaults from JNI
> ------------------------
>
> Key: HBASE-18541
> URL: https://issues.apache.org/jira/browse/HBASE-18541
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Ted Yu
>
> retry-test and multi-retry-test fails flakily when run with
> {code}
> buck test --all --no-results-cache
> {code}
> or when run in a loop:
> {code}
> for i in `seq 1 10`; do buck test --no-results-cache core:retry-test || break
> 1; done
> {code}
> The problem seems to be within the JNI internals and usually happens at the
> create table method call. I was not able to inspect much, but the comments in
> our mini-cluster indicate that we may need to use global references instead
> of local ones. I suspect the problem happens when there is a GC run for the
> test since the failure happens usually after some time (but almost always in
> create table method).
> [~ted_yu] do you mind taking a look at this.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
