7 <table><colgroup><col width="50%"><col width="50%"></colgroup><tbody valign="top"><tr><td><h3>High-level Operations</h3>
9 High-level cluster operations consist primarily of starting, stopping, and
10 restarting a cluster with the ``ceph`` service; checking the cluster's health;
11 and, monitoring an operating cluster.
24 </td><td><h3>Data Placement</h3>
26 Once you have your cluster up and running, you may begin working with data
27 placement. Ceph supports petabyte-scale data storage clusters, with storage
28 pools and placement groups that distribute data across the cluster using Ceph's
47 </td></tr><tr><td><h3>Low-level Operations</h3>
49 Low-level cluster operations consist of starting, stopping, and restarting a
50 particular daemon within a cluster; changing the settings of a particular
51 daemon or subsystem; and, adding a daemon to the cluster or removing a daemon
52 from the cluster. The most common use cases for low-level operations include
53 growing or shrinking the Ceph cluster and replacing legacy or failed hardware
61 Command Reference <control>
67 </td><td><h3>Troubleshooting</h3>
69 Ceph is still on the leading edge, so you may encounter situations that require
70 you to evaluate your Ceph configuration and modify your logging and debugging
71 settings to identify and remedy issues you are encountering with your cluster.
76 ../troubleshooting/community
77 ../troubleshooting/troubleshooting-mon
78 ../troubleshooting/troubleshooting-osd
79 ../troubleshooting/troubleshooting-pg
80 ../troubleshooting/log-and-debug
81 ../troubleshooting/cpu-profiling
82 ../troubleshooting/memory-profiling
89 </td></tr></tbody></table>