Great discussion! Going back to the point of about using CM Vs local "service commands", I find the following about one of my data nodes in my 20+ node cluster:
1. 6 roles (HDFS, YARM, Maprduce, HBase, etc)
2. No running services (via service --status-all, or chkconfig --list)
3. Serveral processes (ps -ef | grep cloudera) - running through "/usr/java/jdk1.7.0_67-cloudera/bin/java"
Given this, I have to manage the cluster using CM only.
Additionally, I have two 1-node pseudo clusters with CDH 5.2 and 5.3. I have to manage these installation through "services".
So there are 2 methods of deployment for CDH, Packages (which is deprecated) and Parcels (which is the preferred method).
Nauseous, it sounds like you might have a mixed deployment type? If you have the cdh RPM packages present on the system, but have deployed CDH through parcels as well, there is probably significant issues with getting CM to manage configuration properly (the deploy client configurations from CM is not going to pass to the generic /etc/* paths the server based configuration parameters).
This content here will be critical reading for you on the design of CM and its approach to managing CDH
Also for everyone please keep in mind we have free training video content from university.cloudera.com on CM for folks to self educate from, here: