[ 
https://issues.apache.org/jira/browse/IMPALA-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476294#comment-16476294
 ] 

Andre Araujo commented on IMPALA-6037:
--------------------------------------

Hi [~mmokhtar],

Is there anything needed to progress on this request? Need some repro?

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org

Reply via email to