[IMPALA-928] Impala daemons leaving behind empty impala_staging cgroups

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: Impala 1.3
• Component/s: Backend
• Labels: llama ramp-up resource-management
• Target Version: Impala 2.5.0
• Assignee: Unassigned
• Reporter: Henry Robinson
• Created: 28/Mar/14 00:33
• Updated: 04/Jan/17 23:58
• Resolved: 03/Feb/16 22:56

Description

I have the following RM options enabled in my impalad:

-state_store_host=adar-1.ent.cloudera.com
-llama_host=adar-1.ent.cloudera.com
-llama_port=15000
-enable_rm=true
-pool_conf_file=pool-acls.txt
-cgroup_hierarchy_path=/var/run/cloudera-scm-agent/cgroups/cpu/hadoop-yarn

When I start impalad via CM, an impala_staging cgroup is created under hadoop-yarn. When I stop it, the impala_staging cgroup remains.
The CM agent should (and will) clean up empty sub-cgroups, but as a good citizen, impalad ought to clean up its own created cgroups when it is stopped.
CM says my impala version is "1.2.0+cdh5.0.0+0".