[IMPALA-4671] Replace kudu::ServicePool with one that uses Impala threads

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 2.8.0
• Fix Version/s: Impala 2.11.0
• Component/s: Distributed Exec
• Target Version: Product Backlog
• Assignee: Sailesh Mukil
• Reporter: Henry Robinson
• Created: 15/Dec/16 17:51
• Updated: 14/Dec/17 23:50
• Resolved: 08/Dec/17 11:36

Description

Kudu's ServicePool uses Kudu's Thread class to service RPC requests. While this works well, the threads it creates aren't monitored by Impala's ThreadMgr subsystem.

Eventually we'd like to standardise on one thread class between projects, but for now it would be useful to reimplement ServicePool in terms of our thread class.

The reactor threads and acceptor threads will still be Kudu threads, but those are less likely to do substantial work, so having them missing from monitoring isn't a big problem.

Issue Links

• blocks: IMPALA-6269 [observability] Add KRPC metrics to /rpcz and /metrics debug webpages