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.
25 </td><td><h3>Data Placement</h3>
27 Once you have your cluster up and running, you may begin working with data
28 placement. Ceph supports petabyte-scale data storage clusters, with storage
29 pools and placement groups that distribute data across the cluster using Ceph's
49 </td></tr><tr><td><h3>Low-level Operations</h3>
51 Low-level cluster operations consist of starting, stopping, and restarting a
52 particular daemon within a cluster; changing the settings of a particular
53 daemon or subsystem; and, adding a daemon to the cluster or removing a daemon
54 from the cluster. The most common use cases for low-level operations include
55 growing or shrinking the Ceph cluster and replacing legacy or failed hardware
65 Command Reference <control>
71 </td><td><h3>Troubleshooting</h3>
73 Ceph is still on the leading edge, so you may encounter situations that require
74 you to evaluate your Ceph configuration and modify your logging and debugging
75 settings to identify and remedy issues you are encountering with your cluster.
80 ../troubleshooting/community
81 ../troubleshooting/troubleshooting-mon
82 ../troubleshooting/troubleshooting-osd
83 ../troubleshooting/troubleshooting-pg
84 ../troubleshooting/log-and-debug
85 ../troubleshooting/cpu-profiling
86 ../troubleshooting/memory-profiling
93 </td></tr></tbody></table>