@herdrick: no it's actually just fine to do it in the order Harsh mentioned. CM will automatically deploy the configurations you specify on the Configuration tab of a service to that service's roles when you restart the service. For example, if you modify a datanode specific property in CM, save the change and restart the service, then all the datanodes will get new copies of their hdfs-site.xml files upon startup. The only reason to deploy the client configs that Harsh mentioned is for external client apps that want to utilize the cluster. If you made changes that will affect the behavior of clients, then the client configs need to be re-deployed. This can happen after the services are restarted, but before you attempt to reconnect to the cluster with your client app. I hope that clears it up.
Clint
... View more
