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.
23 </td><td><h3>Data Placement</h3>
25 Once you have your cluster up and running, you may begin working with data
26 placement. Ceph supports petabyte-scale data storage clusters, with storage
27 pools and placement groups that distribute data across the cluster using Ceph's
44 </td></tr><tr><td><h3>Low-level Operations</h3>
46 Low-level cluster operations consist of starting, stopping, and restarting a
47 particular daemon within a cluster; changing the settings of a particular
48 daemon or subsystem; and, adding a daemon to the cluster or removing a daemon
49 from the cluster. The most common use cases for low-level operations include
50 growing or shrinking the Ceph cluster and replacing legacy or failed hardware
58 Command Reference <control>
64 </td><td><h3>Troubleshooting</h3>
66 Ceph is still on the leading edge, so you may encounter situations that require
67 you to evaluate your Ceph configuration and modify your logging and debugging
68 settings to identify and remedy issues you are encountering with your cluster.
73 ../troubleshooting/community
74 ../troubleshooting/troubleshooting-mon
75 ../troubleshooting/troubleshooting-osd
76 ../troubleshooting/troubleshooting-pg
77 ../troubleshooting/log-and-debug
78 ../troubleshooting/cpu-profiling
79 ../troubleshooting/memory-profiling
86 </td></tr></tbody></table>