You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Chia-Ping Tsai (JIRA)" <ji...@apache.org> on 2018/01/30 22:36:00 UTC

[jira] [Created] (HBASE-19900) The failed op is added to RetriesExhaustedWithDetailsException repeatedly

Chia-Ping Tsai created HBASE-19900:
--------------------------------------

             Summary: The failed op is added to RetriesExhaustedWithDetailsException repeatedly 
                 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


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
(v7.6.3#76005)