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

Duo Zhang commented on HBASE-17323:
-----------------------------------

I can get the same result with [~tedyu]. If I update to the version before 
HBASE-17081
{noformat}
commit 401e83cee383508a2ccdf5b92e7c77a0be2e566a
Author: tedyu <yuzhih...@gmail.com>
Date:   Thu Dec 15 07:06:37 2016 -0800

    HBASE-17318 Increment does not add new column if the increment amount is 
zero at first time writing (Guangxu Cheng)
{noformat}

TestAsyncGetMultiThread have passed all the 10 runs.

If I update to HBASE-17081
{noformat}
commit a2a7618d261bfe121f05821d89242d770cd7b7ec
Author: Ramkrishna <ramkrishna.s.vasude...@intel.com>
Date:   Thu Dec 15 22:02:05 2016 +0530

    HBASE-17081 Flush the entire CompactingMemStore content to disk (Anastasia
    Braginsky)
{noformat}

It failed 7 times out of 10 runs.

So I think the problem is HBASE-17081.

> TestAsyncGetMultiThread fails in master
> ---------------------------------------
>
>                 Key: HBASE-17323
>                 URL: https://issues.apache.org/jira/browse/HBASE-17323
>             Project: HBase
>          Issue Type: Test
>            Reporter: Ted Yu
>         Attachments: 17323.hack.txt, testAsyncGetMultiThread-output.gz
>
>
> From 
> https://builds.apache.org/job/HBase-Trunk_matrix/2137/jdk=JDK%201.8%20(latest),label=Hadoop/testReport/junit/org.apache.hadoop.hbase.client/TestAsyncGetMultiThread/test/
>  :
> {code}
> java.util.concurrent.ExecutionException: java.lang.NullPointerException
>       at org.apache.hadoop.hbase.util.Bytes.toInt(Bytes.java:1003)
>       at org.apache.hadoop.hbase.util.Bytes.toInt(Bytes.java:980)
>       at 
> org.apache.hadoop.hbase.client.TestAsyncGetMultiThread.run(TestAsyncGetMultiThread.java:108)
>       at 
> org.apache.hadoop.hbase.client.TestAsyncGetMultiThread.lambda$null$1(TestAsyncGetMultiThread.java:122)
> {code}
> This can be reproduced locally.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to