Support Questions
Find answers, ask questions, and share your expertise

Impala executors and coordinators

Explorer

Hi, 

 

What is the difference in impala executors and impala coordinators ?  Which one shall I increase in order to run my query faster ?

 

Thanks in advance

1 ACCEPTED SOLUTION

Accepted Solutions

Super Collaborator

Hello @drgenious 

 

Thanks for using Cloudera Community. We hope the response by @balajip was helpful for your ask. Additionally, We wish to share a few details:

 

  • Your Question points to "How To Make Query Faster". Ideally, Impala would use Parallelism for executing a Query in fragments across Executors. As such, the 1st review should be using Impala Query Profile of the SQL to identify the Time taken at each Phase of SQL Execution. Refer [1] & [2] for few Links around Impala Query Profile. 
  • Once the Phase taking the Most Time is identified, Fine-Tune accordingly. Simply increasing the Impala Executors Daemon or using a Dedicated Coordinator may not be helpful, unless the SQL's Slow Fragment(s) are identified. 

 

Kindly review & let us know if you have any further ask in the Post. 

 

Regards, Smarak

 

[1] https://cloudera.ericlin.me/2018/09/impala-query-profile-explained-part-1/

[2] https://docs.cloudera.com/runtime/7.2.10/impala-reference/topics/impala-profile.html

View solution in original post

2 REPLIES 2

Cloudera Employee

@drgenious From where you connect with impala-shell that will act as impala coordinator other impala damonens are executors.
If you configured a dedicated coordinator that daemon won't execute any fragments.
For more information about dedicated coordinator please refer to the below doc.
https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/impala_dedicated_coordinator.html

Super Collaborator

Hello @drgenious 

 

Thanks for using Cloudera Community. We hope the response by @balajip was helpful for your ask. Additionally, We wish to share a few details:

 

  • Your Question points to "How To Make Query Faster". Ideally, Impala would use Parallelism for executing a Query in fragments across Executors. As such, the 1st review should be using Impala Query Profile of the SQL to identify the Time taken at each Phase of SQL Execution. Refer [1] & [2] for few Links around Impala Query Profile. 
  • Once the Phase taking the Most Time is identified, Fine-Tune accordingly. Simply increasing the Impala Executors Daemon or using a Dedicated Coordinator may not be helpful, unless the SQL's Slow Fragment(s) are identified. 

 

Kindly review & let us know if you have any further ask in the Post. 

 

Regards, Smarak

 

[1] https://cloudera.ericlin.me/2018/09/impala-query-profile-explained-part-1/

[2] https://docs.cloudera.com/runtime/7.2.10/impala-reference/topics/impala-profile.html

View solution in original post