[HBASE-13906] Improve handling of NeedUnmanagedConnectionException

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0, 1.1.0
• Fix Version/s: 1.2.0, 1.3.0
• Component/s: API, Client
• Release Note: With this patch NeedUnmanagedConnectionException is effectively treated as non-retryable exception, but for backwards compatibility purposes we don't throw it directly, but instead wrap into DoNotRetryIOException when we return error to the caller.
• Assignee: Mikhail Antonov
• Reporter: Nick Dimiduk
• Created: 15/Jun/15 19:08
• Updated: 24/Jun/22 19:25
• Resolved: 23/Jun/15 06:53

Description

During my investigation of HBASE-13833, I made this comment

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.

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.

Issue Links

• is related to: HBASE-13833 LoadIncrementalHFile.doBulkLoad(Path,HTable) doesn't handle unmanaged connections when using SecureBulkLoad