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

Hudson commented on HBASE-16866:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #1811 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1811/])
HBASE-16866 Avoid NPE in AsyncRequestFutureImpl#updateStats (ChiaPing (tedyu: 
rev 6c89c6251ff611c2f10bfd6f8c9f8a2d717dc71b)
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncRequestFutureImpl.java


> Avoid NPE in AsyncRequestFutureImpl#updateStats
> -----------------------------------------------
>
>                 Key: HBASE-16866
>                 URL: https://issues.apache.org/jira/browse/HBASE-16866
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: ChiaPing Tsai
>            Assignee: ChiaPing Tsai
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16866.v0.patch, HBASE-16866.v1.patch
>
>
> If region disables the stats, it won’t response any 
> ClientProtos.RegionLoadStats to client. So the NPE will happen in 
> AsyncRequestFutureImpl#updateStats.
> We should use relevant log instead of NPE because the data manipulation 
> shouldn’t be broken by statistics.
> {noformat}
>   protected void updateStats(ServerName server, Map<byte[], 
> MultiResponse.RegionResult> results) {
>       …
>       ClientProtos.RegionLoadStats stat = regionStats.getValue().getStat();
>       RegionLoadStats regionLoadstats = 
> ProtobufUtil.createRegionLoadStats(stat);
>       …
>   }
> {noformat}



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

Reply via email to