You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2015/06/15 21:09:00 UTC

[jira] [Created] (HBASE-13906) Improve handling of NeedUnmanagedConnectionException

Nick Dimiduk created HBASE-13906:
------------------------------------

             Summary: Improve handling of NeedUnmanagedConnectionException
                 Key: HBASE-13906
                 URL: https://issues.apache.org/jira/browse/HBASE-13906
             Project: HBase
          Issue Type: Bug
    Affects Versions: 1.1.0, 1.0.0
            Reporter: Nick Dimiduk
             Fix For: 1.2.0


During my investigation of HBASE-13833, I made this [comment|https://issues.apache.org/jira/browse/HBASE-13833?focusedCommentId=14585302&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14585302]

{quote}
One other thing: should we somehow handle NeedUnmanagedConnectionException similarly to DoNotRetryIOException? It's too late to wire them up thusly, but for the case of bulk load when the bug is expressed, we go through the full 35x retry loop before eventually failing the RPC. This would be applicable to branch-1.
{quote}

This would apply only to branch-1 as master no longer has unmanaged connections. Probably we cannot change the inheritance hierarchy due to compatibility guarantees, but maybe we can do something like everywhere we look for DNRIOE, we do the same for NUCE.



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