[ https://issues.apache.org/jira/browse/HBASE-7626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Helmling updated HBASE-7626: --------------------------------- Resolution: Fixed Release Note: Overriding the configured RPC engine separately for each RPC protocol (hbase.rpc.engine.<protocol class> configuration property) is no longer supported. Only a single RPC engine configuration (hbase.rpc.engine) is used. The HConnectionManager#deleteConnection(Configuration, boolean) and HConnectionManager#deleteAllConnections(boolean) methods are now deprecated, as the "stopProxy" parameter is no longer used. In some cases, where clients explicitly manage HConnection instance creation, the number of client RPC connections created may change. This issue changes the HConnection implementation to use it's own managed HBaseClient instance, with its own set of client RPC connections. So explicitly creating multiple HConnection instances (using HConnectionManager.createConnection()) will result in multiple HBaseClient instances. However, for the default behavior, using HTable with a single Configuration, there is no change. Status: Resolved (was: Patch Available) Committed to 0.94 branch. Thanks for reviews, Ted and Lars! > Backport portions of HBASE-7460 to 0.94 > --------------------------------------- > > Key: HBASE-7626 > URL: https://issues.apache.org/jira/browse/HBASE-7626 > Project: HBase > Issue Type: Sub-task > Components: Client, IPC/RPC > Reporter: Lars Hofhansl > Assignee: Gary Helmling > Priority: Critical > Fix For: 0.94.5 > > Attachments: HBASE-7626-2_0.94.patch > > > Marking critical so it gets in. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira