[jira] [Resolved] (IMPALA-4671) Replace kudu::ServicePool with one that uses Impala threads

["Sailesh Mukil (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sailesh Mukil resolved IMPALA-4671.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.12.0

Commits are in:
https://github.com/apache/impala/commit/a94d6068c757912eaa741db82331ef72e5696004
https://github.com/apache/impala/commit/82267a2779da2165802195ba202223d2c205b73d

> Replace kudu::ServicePool with one that uses Impala threads
> -----------------------------------------------------------
>
>                 Key: IMPALA-4671
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4671
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Distributed Exec
>    Affects Versions: Impala 2.8.0
>            Reporter: Henry Robinson
>            Assignee: Sailesh Mukil
>             Fix For: Impala 2.12.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)