hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-16866) Avoid NPE in AsyncRequestFutureImpl#updateStats
Date Tue, 18 Oct 2016 18:11:59 GMT

     [ https://issues.apache.org/jira/browse/HBASE-16866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ted Yu updated HBASE-16866:
---------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Thanks for the patch, ChiaPing

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

Mime
View raw message