[HBASE-13252] Get rid of managed connections and connection caching - ASF JIRA

XML

Word

Printable

JSON

Hadoop Flags:

Reviewed
Release Note:

Hide
For a long time, HBase supported 2 types of connections - managed, which were cached and closed automatically when not needed, and unmanaged, where user is responsible for closing the connections by calling #close() on them.

The concept of managed connections in HBase (deprecated before) has now been extinguished completely, and now all callers are responsible for managing the lifecycle of connections they acquire.

Show
For a long time, HBase supported 2 types of connections - managed, which were cached and closed automatically when not needed, and unmanaged, where user is responsible for closing the connections by calling #close() on them. The concept of managed connections in HBase (deprecated before) has now been extinguished completely, and now all callers are responsible for managing the lifecycle of connections they acquire.

(Need to):

Remove CONNECTION_INSTANCES from ConnectionManager
Remove HConnectionKey
Remove 'managed' property from ClusterConnection, HCI and places where it's used now
AFAIS this property isn't visible to client (ClusterConnection is private interface), so technically this would not even be backward-incompatible change, and no release note needed?
In fact, ConnectionManager can be removed, too.

is related to

HBASE-13328 LoadIncrementalHFile.doBulkLoad(Path,HTable) should handle managed connections

HBASE-13349 Reduce NeedUnmanagedConnectionException issues