Hi Daniel

Thank you very much for the support.

* When you say that the feature can be turned
off, do you mean resource types or resource profiles?  I know there's an
off-by-default property that governs resource profiles, but I didn't see
any way to turn off resource types.
Yes,*yarn.resourcemanager.resource-profiles.enabled* is false by default
and controls off/on of this feature. Now regarding new resource types, its
been loaded from "*resource-types.xml"* and by default this XML file is not
available in the package. Thus prevents any issues in default case. Once
this file is added to a cluster then new resources will be loaded from same.

* Even if only CPU and memory are configured, i.e. no additional resource
types, the code path is different than it was.
Earlier primitive data types were used to represent vcores and memory. As
per resource profile work, all resources under YARN is categorized as
ResourceInformation and placed under existing Resource object. So memory
and vcores will be accessible and operable with same set of public apis
from Resources or ResourceCalculator (DRC) same as earlier even when
feature is off (Code path is same, but improved to support a unified
ResourceInformation class instead of memory/vcores primitive types).

On Sat, Aug 26, 2017 at 8:10 PM Daniel Templeton <[EMAIL PROTECTED]>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB