Configuration in Cloudera Manager not reflected in yarn-site.xml

[#1]

I am trying to increase the maximum memory available for containers. In Couldera Manager (CDH5), I set the configuration: 

Container Memory Maximum (yarn.scheduler.maximum-allocation-mb) to 64GB, save changes, and restart all Yarn role instances.  When inspecting the file 

/opt/cloudera/parcels/CDH-5.3.0-1.cdh5.3.0.p0.30/lib/hadoop/etc/hadoop/yarn-site.xml, I still see the original value of 

7584MB. Could you please let me know what I am missing? How do I test if a configuraiton value is actually in effect?

[#2 · Accepted solution]

The files within the parcel are not modified after installation. When you
make configuration changes and restart the role, Cloudera Manager will send
the updated files to the agent which will stash it under
/var/run/cloudera-scm-agent/process. Any client configuration changes will
appear in /etc//conf

You can read about how Cloudera Manager manages roles and services in this
blog post.
http://blog.cloudera.com/blog/2013/07/how-does-cloudera-manager-work/