Enis Soztutar commented on HBASE-18541:

bq. core/async-batch-rpc-retrying-multi-region-test.cc appeared in stack 
trace.However, I don't find this file.
I had broken down the test into two, but that patch is not committed. You don't 
need to worry about that for now. Just running the multi-retry test in a loop 
reproduces the problem. You can install openjdk-8-dbg if you want to see the 
stack traces inside JVM. 
bq. Can we sync up HBASE-14850 branch with the master branch ?
We will resync sometime soon, because testing needs a more stable server-side 
that what the branch has as of now. For debugging this issue though, it should 
not be needed. 
bq. However, AsyncRpcRetryTest.TestFailWithOperationTimeout passes when run 
As per the description, the tests fail flakily, and is probably due to GC (not 
confirmed). Running the test in a loop like the one in the description 
reproduces the problem. 

> [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

Reply via email to