[HBASE-13036] Meta scanner should use its own threadpool

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.0, 2.0.0
• Assignee: Devaraj Das
• Reporter: Devaraj Das
• Created: 13/Feb/15 01:18
• Updated: 03/Jun/15 15:29
• Resolved: 18/Feb/15 19:01

Description

Currently, during region location lookups, the meta is scanned and for this the scanner submits a request to the thread pool of the table in question. Sometimes, it might happen that many scan requests are simultaneously submitted on the table - let's say 256, and this is the max size of the thread pool. Each of these scan requests would in turn submit meta scan requests on the same thread pool, but they will be in the queue. The meta scans will not happen and the original table scans would lock up. The meta scans should use a different thread pool.

Issue Links

• relates to: HBASE-13460 Revise the MetaLookupPool executor-related defaults (introduced in HBASE-13036)