Tenants are users of the cluster. Lets say you have app teams/users named dev-a, dev-b, dev-c using the cluster,  you will be estimating what resource each team will likely consume and create queue/pool to them with appropriate capacity.  With regards to hierarchy, root would be the top most parent (represents the overall cluster resource) and you will create leaf queues/pool configured with the min/max resources you want to allocate for individual team. Applications gets assigned to the leaf queue and utilize the respective queue resource.   With the utilization report you will have an idea of how much each team had used in its respective queue/pool. "There are no details about hierarchy of the utilization report" --> Are you referring to knowing utilisation at root plus all the leaf queues? https://docs.cloudera.com/cdp-private-cloud-base/7.1.9/monitoring-and-diagnostics/topics/cm-use-cluster-utilization-report-manage-resources.html in the picture shared in this doc you will see an example of overall cluster utilization and the breakup of utilization across individual queues. https://blog.cloudera.com/yarn-capacity-scheduler/ ... View more

Inorder for KDC to allow a client, it must be trusted. Unfortunately you need to have the principle trusted through cross realm trust to allow a client from different KDC  ... View more

Glad you resolved the issue. Just to add more context, The error indicates agent was unable to monitor the filesystem, likely the nfs is stuck. This results in agent to be stuck in monitoring the filesystem and unable to heartbeat to CM server. Hence Removing the NFS from monitored filesystem helped to resolve the issue.  ... View more