[HBASE-9917] Fix it so Default Connection Pool does not spin up max threads even when not needed

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.98.0, 0.96.1
• Component/s: Client
• Hadoop Flags: Reviewed
• Assignee: Michael Stack
• Reporter: Michael Stack
• Created: 08/Nov/13 00:11
• Updated: 16/Dec/13 18:46
• Resolved: 12/Nov/13 04:56

Description

Testing, I noticed that if we use the HConnection executor service as opposed to the executor service that is created when you create an HTable without passing in a connection: i.e

HConnectionManager.createConnection(config).getTable(tableName)

vs

HTable(config, tableName)

... then we will spin up the max 256 threads and they will just hang out though not being used.

We are encouraging HConnection#getTable over new HTable so worth fixing.