hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18541) [C++] Segfaults from JNI
Date Fri, 08 Sep 2017 02:07:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158016#comment-16158016

Enis Soztutar commented on HBASE-18541:

Thanks for the patch. A short term fix is acceptable, since we seem to be having some trouble
finding the actual issue in the JNI layer. Can you please remove commented out code. 
-  auto tableName = createTestTable(split_regions, table_name);
+// auto tableName = createTestTable(split_regions, table_name);
Do we need a similar change in regular retry-test as well? 

> [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
>         Attachments: 18541.v1.txt, 18541.v3.txt, 1-table-async-test.txt
> 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

View raw message