About kratka

kratka · ‎08-15-2018

thank you @nicusan will give it a try

kratka · ‎08-13-2018

@Cloudera can anyone help us in this regard? thank you.

kratka · ‎08-13-2018

assigning resources under resources tab will be per host. We need to limit cpu at impala cluster level. And we are not using static pools we are using dynamic pools cpu.shares will not be helpful i believe.

kratka · ‎08-09-2018

Also we have set --num-scanner-threads to 52 assuming 1 thread per core. We have 28 core cpu with hyper threading enabled.

kratka · ‎08-09-2018

How do we control the number of cores used by impala. Currently we are running yarn and impala work load but impala queries are cpu intensive and ends up using most of the available cpu cores on the system.

kratka · ‎08-09-2018

Hi, We have a 32 node impala cluster where each node is both an executor and a coordinator. We wanted to dedicate 6 nodes as co-ordinators and the rest as executors. We created two config groups and set is_executor=false for coordinators and is_coordinator=false for executors and we restarted the impala service. We deleted a table and tried to recreate it we got an error saying the table already exist. We would like to know how to refresh the metadata on all the nodes.

Online	Offline
Last Visited	‎08-22-2018 12:23 PM

Member Since	‎07-16-2018 08:25 AM
Last Visited	‎08-22-2018 12:23 PM
Posts	6
Kudos received	2

Cloudera Community

Re: impala dedicated co-ordinator and executor

Re: impala dedicated co-ordinator and executor

Re: control cpu usage by impala

Re: control cpu usage by impala

control cpu usage by impala

impala dedicated co-ordinator and executor