Can the impalad "idle_query_timeout" parameter be set within Cloudera Manager?

[#1]

We'd like to reduce the number of idle impala query sessions. Can the impalad "idle_query_timeout" parameter be set within Cloudera Manager or does it have to be set within each impalad node?

[#2]

Yes, that's certainly possible.

In CM, select your "Impala Daemon" configuration and look for the option:

"Impala Daemon Command Line Argument Advanced Configuration Snippet (Safety Valve)"

In that box, you can set command line arguments to be passed to the impalad when it starts up. For example, you would add

-idle_session_timeout=10

for a 10s timeout.

Remember to restart all impalads are changing any such start-up option.

[#3 · Accepted solution]

To set this property via CM, go to CM > Impala > Configuration > Impala Daemon > Advanced > Impala Daemon Command Line Argument Advanced Configuration Snippet (Safety Valve) and add the below: -idle_query_timeout= Restart the impalads after saving the above change.

[#4]

Can this be set for queries submitted via HUE in Impala Editor?

What would be the exact config name/structure and which advanced snippet would it go in?

[#5]

@siddesh210491the simplest solution might be to set the safety valve globally as above. That will apply globally but may be a reasonable setting for clients other than hue too.

Otherwise another option is to use the query_timeout_s query option. You can set a default value for that option (or any query options) if you have dynamic resource pools set up, with all Hue queries going into a pool.

https://www.cloudera.com/documentation/enterprise/latest/topics/cm_mc_resource_pools.html#concept_xk...