@BenK,   Cloudera Manager's steps for starting servers are based on internal dependencies, so there isn't a configuration in Cloudera Manager that could be used to change it.  I suspect that the StreamSets fix may have been around dependencies, in the CSD, but that's just a guess.   The only alternative I can see at this time is to bring the services up one at a time. You could do that with the API and wrap it in the script:   https://cloudera.github.io/cm_api/apidocs/v14/path__clusters_-clusterName-_services_-serviceName-_commands_start.html   You can see all REST API stuff here: https://cloudera.github.io/cm_api/apidocs/v14/   For instance, you could write a shell script that executes a serice of "curl" commands that start the services. There is a complexity in that you need to wait till the service is really running before started, but that can be accomplished by using:   https://cloudera.github.io/cm_api/apidocs/v14/path__clusters_-clusterName-_services_-serviceName-.html   and parsing out the status.  If a service is "STARTED" start the next one...   "serviceState" : "STARTED",   It might be something to play with if you are stuck in this state long term.  The API is in Java and Python and you can find examples of usage here too: https://cloudera.github.io/cm_api/ ... View more