diff options
author | John Wilkins <john.wilkins@inktank.com> | 2013-04-30 18:04:46 -0700 |
---|---|---|
committer | John Wilkins <john.wilkins@inktank.com> | 2013-04-30 18:04:46 -0700 |
commit | b17e8424e88eb14a89a3b2ea4890b121904a82d6 (patch) | |
tree | 6cca3caed6cb96fe962e80ae1f831fa92bf9b3ec | |
parent | bd6ea8d02cfdafb73e0b8c6a0654e436a7a62057 (diff) | |
download | ceph-b17e8424e88eb14a89a3b2ea4890b121904a82d6.tar.gz |
doc: Incorporating Tamil's feedback.
Signed-off-by: John Wilkins <john.wilkins@inktank.com>
-rw-r--r-- | doc/install/upgrading-ceph.rst | 21 |
1 files changed, 15 insertions, 6 deletions
diff --git a/doc/install/upgrading-ceph.rst b/doc/install/upgrading-ceph.rst index 2c1a1922e37..667a9e235b9 100644 --- a/doc/install/upgrading-ceph.rst +++ b/doc/install/upgrading-ceph.rst @@ -164,8 +164,15 @@ Bobtail to Cuttlefish Upgrading your cluster from Bobtail to Cuttlefish has a few important considerations. First, the monitor uses a new architecture, so you should -upgrade the full set of monitors to use Cuttlefish. Second, ensure metadata -servers have unique names. See the following sections for details. +upgrade the full set of monitors to use Cuttlefish. Second, if you run multiple +metadata servers in a cluster, ensure the metadata servers have unique names. +See the following sections for details. + +Replace any ``apt`` reference to older repositories with a reference to the +Cuttlefish repository. For example:: + + sudo rm /etc/apt/sources.sources.list.d/ceph.list + echo deb http://ceph.com/debian-cuttlefish/ $(lsb_release -sc) main | sudo tee /etc/apt/sources.list.d/ceph.list Monitor @@ -186,10 +193,12 @@ monitors in immediate succession. MDS Unique Names ---------------- -The monitor now enforces that MDS names be unique. If you have multiple daemons -start with with the same id (e.g., mds.a) the second one will implicitly mark -the first as failed. Multi-MDS configurations with identical names must be -adjusted accordingly to give daemons unique names. +The monitor now enforces that MDS names be unique. If you have multiple metadata +server daemons that start with with the same ID (e.g., mds.a) the second +metadata server will implicitly mark the first metadata server as ``failed``. +Multi-MDS configurations with identical names must be adjusted accordingly to +give daemons unique names. If you run your cluster with one metadata server, +you can disregard this notice for now. Upgrade Procedures |