hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-18188) [C++] Fix Handling do not retry exceptions
Date Thu, 08 Jun 2017 01:21:20 GMT
Enis Soztutar created HBASE-18188:

             Summary: [C++] Fix Handling do not retry exceptions
                 Key: HBASE-18188
                 URL: https://issues.apache.org/jira/browse/HBASE-18188
             Project: HBase
          Issue Type: Sub-task
            Reporter: Enis Soztutar
            Assignee: Enis Soztutar

Needed for HBASE-18061 and others. 

Java client relies on the exception hierarchy for DoNotRetryExceptions, which there is 40+
subtypes. The exceptions from the server side are rethrown in the client side (ConnectionUtils.translateException,
etc) and the rest of the code deals with do-not-retry information by catching DoNotRetryIOException's
(thus relying on exception hierarchy). 

This of course does not work on the C++ side, since we lack the info for the java class types.
In case the exception happens in the RPC response, the server puts the do_not_retry information
as a field in PB (see ExceptionResponse::do_not_retry PB message). However, in other settings,
we just serialize the exception without do_not_retry information (see ResultOrException PB
message). In some other settings, we can raise exceptions from the client-side (for example
when table cannot be found in meta). 

We need a strategy to handle do-not-retry information uniformly, no matter they are coming
from client side or server side. 

This message was sent by Atlassian JIRA

View raw message