[HBASE-14478] A ThreadPoolExecutor with a LinkedBlockingQueue cannot execute tasks concurrently

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: regionserver
• Hadoop Flags: Reviewed
• Assignee: Jingcheng Du
• Reporter: Jingcheng Du
• Created: 24/Sep/15 06:35
• Updated: 01/Jul/22 21:35
• Resolved: 25/Sep/15 17:46

Description

In FlushTableSubprocedurePool and SnapshotSubprocedurePool, the ThreadPoolExecutor with a LinkedBlockingQueue is used, and it's corePoolSize and maximumPoolSize are not the same, which can cause the if the number of tasks is larger than corePoolSize, those tasks cannot be executed until old tasks are finished and the number of running tasks is less than corePoolSize. We should use the same value for the corePoolSize and maximumPoolSize if the LinkedBlockingQueue is used.

Issue Links

• is related to: HBASE-15784 Misuse core/maxPoolSize of LinkedBlockingQueue in ThreadPoolExecutor