Starting, Stopping, and Restarting Cloudera Manager Agents
To start Agents, the supervisord process, and all managed service processes, use one of the following commands:
$ sudo service cloudera-scm-agent start
$ sudo service cloudera-scm-agent clean_startThe directory /var/run/cloudera-scm-agent is completely cleaned out; all files and subdirectories are removed, and then the start command is executed. /var/run/cloudera-scm-agent contains on-disk running Agent state. Some Agent state is left behind in /var/lib/cloudera-scm-agent, but you shouldn't delete that. For further information, see Server and Client Configuration and Process Management.
Stopping and Restarting Agents
To stop or restart Agents while leaving the managed processes running, use one of the following commands:
$ sudo service cloudera-scm-agent stop
$ sudo service cloudera-scm-agent restart
Hard Stopping and Restarting Agents
: The hard_stop, clean_restart, or hard_restart commands kill all running managed service processes on
the host(s) where the command is run.
To stop or restart Agents, the supervisord process, and all managed service processes, use one of the following commands:
$ sudo service cloudera-scm-agent hard_stop
$ sudo service cloudera-scm-agent hard_restartHard restart is useful for the following situations:
- You're upgrading Cloudera Manager and the supervisord code has changed between your current version and the new one. To properly do this upgrade you'll need to restart supervisor too.
- supervisord is hung and needs to be restarted.
- You want to clear out all running state pertaining to Cloudera Manager and managed services.
$ sudo service cloudera-scm-agent clean_restartRuns hard_stop followed by clean_start.
Checking Agent Status
To check the status of the Agent process, use the command:
$ sudo service cloudera-scm-agent status
|<< Moving the Cloudera Manager Server to a New Host||Configuring Cloudera Manager Agents >>|