hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chia-Ping Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19900) Region-level exception destroy the result of batch
Date Sat, 03 Feb 2018 15:28:00 GMT

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

Chia-Ping Tsai commented on HBASE-19900:

Seems some tests expect that failed ops in RetriesExhaustedWithDetailsException will have
the different exceptions. 

> Region-level exception destroy the result of batch
> --------------------------------------------------
>                 Key: HBASE-19900
>                 URL: https://issues.apache.org/jira/browse/HBASE-19900
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Critical
>             Fix For: 1.3.2, 1.5.0, 1.2.7, 2.0.0-beta-2, 1.4.2
>         Attachments: HBASE-19900.v0.patch
> 1) decrease action count repeatedly
> If the AsyncRequestFuture#waitUntilDone return prematurely, user will get the incorrect
results. Or user will be block by AsyncRequestFuture#waitUntilDone as the count is never
equal with 0.
> 2) the successive result will be overwrited 
> 3) The failed op is added to RetriesExhaustedWithDetailsException repeatedly 
> AsyncRequestFutureImpl#receiveMultiAction process the action-lever error first, and then
add the region-level exception to each action. Hence, user may get the various exceptions
for the same action (row op) from the RetriesExhaustedWithDetailsException.
> In fact, if both of action-level exception and region-lever exception exist, they always
have the same context. I'm not sure whether that is what RetriesExhaustedWithDetailsException want.
As i see it, we shouldn't have the duplicate ops in RetriesExhaustedWithDetailsException
since that may confuse users if they catch the RetriesExhaustedWithDetailsException to check
the invalid operations.

This message was sent by Atlassian JIRA

View raw message