You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Juan Yu (JIRA)" <ji...@apache.org> on 2017/10/10 18:43:00 UTC

[jira] [Created] (IMPALA-6037) Frontend should create thread on demand instead of all at front

Juan Yu created IMPALA-6037:
-------------------------------

             Summary: Frontend should create thread on demand instead of all at front
                 Key: IMPALA-6037
                 URL: https://issues.apache.org/jira/browse/IMPALA-6037
             Project: IMPALA
          Issue Type: Improvement
          Components: Frontend
            Reporter: Juan Yu


Impala frontend uses thrift threadpool to handle frontend connections. it will create all threads specified by "fe_service_threads" at Impalad startup no matter if those connections are really used or not.
When not all connections are used, those idle connection threads add overhead especially for short queries. e.g.  fe_service_threads = 600, but only 10 active fe connections. this will create 1200 threads (600 for beewax, 600 for hs2). short query (< 2s) latency increase ~3x compare with  fe_service_threads = 64.
Impala should create fe thread on demand to reduce overhead.



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