This sounds like a possible option, if the auto-restart only relies on the agent, and not the CM server. And also assuming I can kill oozie while CM is down. As stated, "service oozie stop" won't work, since oozie isn't registered as a service on the host. I guess it should be possible to find the process somewhere, but killing it that way doesn't seem all that "nice" to me.   The only issue is that I would like to have oozie connect to a different database after restarting.   As far as I can see the current service settings (like oozie-site.xml) are kept in subdirectories of /var/run/cloudera-scm-agent/process but manually changing those files seems like a pretty sketchy thing to start doing.   Do you have any experience on this type of thing? ... View more

Okay, I found the "inspect all nodes" function. I am not sure what to use it for. All nodes are in good condition.   I am looking for terminal control of Oozie because I would like to test the system while the CM host is down.   Also, there is no /etc/ini.d directory in my cluster. There are /etc/init and /etc/init.d but none of them contain Oozie-related files or directories. ... View more

Thanks for the reply!   On my clusters Oozie and CM installations are not located on the same host. I have multiple clusters, both running on dedicated hardware, and on AWS. All are running CDH 5.4.x or 5.5.x and have the same problem, regarding missing service entries.   When trying "$service oozie restart" I simply get "oozie: unrecognized service". Using "$service --status-all" gives a list of services, on which none of my CDH services are mentioned.   I am not sure what you are referring to with "inspect all the hosts". There are only 6 nodes in my cluster, so manually checking per-node is not a problem.     ... View more