Understanding Ceph service management

Every component of Ceph, whether it's MON, OSD, MDS, or RGW, runs as a service on top of an underlying operating system. As a Ceph storage administrator, you should know about the Ceph services and how to operate them. On Red-Hat-based distributions, Ceph daemons can be managed in different ways: as a traditional SYSVINIT or as a service. Each time you start, restart, and stop Ceph daemons (or your entire cluster), you must specify at least one option and one command. You may also specify a daemon type or a daemon instance. The general syntax for this is as follows:

{ceph service command} [options] [command] [daemons]

The Ceph options include:

  • --verbose or -v: This is for verbose logging.
  • --valgrind: (It's used for Dev and QA only.) This is for valgrind debugging.
  • --allhosts or -a: This executes on all nodes that are mentioned in ceph.conf, otherwise on localhost.
  • --conf or -c: This is to use and alternate the configuration file.
  • --restart: Automatically restarts the daemon if it core dumps.
  • --norestart: This command says to not restart the daemon if it core dumps.

The Ceph commands include the following:

  • status: Shows status of the daemon
  • start: Starts the daemon
  • stop: Stops the daemon
  • restart: Stops and then starts the daemon
  • forcestop: Forces the daemon to stop; similar to kill-9
  • killall: Kills all daemons of a particular type
  • cleanlogs: Cleans out the log directory
  • cleanalllogs: Cleans out everything in the log directory

The Ceph daemons include the following:

  • mon
  • osd
  • msd
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.226.251.206