ceph/doc/cephfs/upgrading.rst

   1 Upgrading the MDS Cluster
   2 =========================
   3
   4 Currently the MDS cluster does not have built-in versioning or file system
   5 flags to support seamless upgrades of the MDSs without potentially causing
   6 assertions or other faults due to incompatible messages or other functional
   7 differences. For this reason, it's necessary during any cluster upgrade to
   8 reduce the number of active MDS for a file system to one first so that two
   9 active MDS do not communicate with different versions.  Further, it's also
  10 necessary to take standbys offline as any new CompatSet flags will propagate
  11 via the MDSMap to all MDS and cause older MDS to suicide.
  12
  13 The proper sequence for upgrading the MDS cluster is:
  14
  15 1. Disable and stop standby-replay daemons.
  16
  17 ::
  18
  19     ceph fs set <fs_name> allow_standby_replay false
  20
  21 In Pacific, the standby-replay daemons are stopped for you after running this
  22 command. Older versions of Ceph require you to stop these daemons manually.
  23
  24 ::
  25
  26     ceph fs dump # find standby-replay daemons
  27     ceph mds fail mds.<X>
  28
  29
  30 2. Reduce the number of ranks to 1:
  31
  32 ::
  33
  34     ceph fs set <fs_name> max_mds 1
  35
  36 3. Wait for cluster to stop non-zero ranks where only rank 0 is active and the rest are standbys.
  37
  38 ::
  39
  40     ceph status # wait for MDS to finish stopping
  41
  42 4. Take all standbys offline, e.g. using systemctl:
  43
  44 ::
  45
  46     systemctl stop ceph-mds.target
  47
  48 5. Confirm only one MDS is online and is rank 0 for your FS:
  49
  50 ::
  51
  52     ceph status
  53
  54 6. Upgrade the single active MDS, e.g. using systemctl:
  55
  56 ::
  57
  58     # use package manager to update cluster
  59     systemctl restart ceph-mds.target
  60
  61 7. Upgrade/start the standby daemons.
  62
  63 ::
  64
  65     # use package manager to update cluster
  66     systemctl restart ceph-mds.target
  67
  68 8. Restore the previous max_mds for your cluster:
  69
  70 ::
  71
  72     ceph fs set <fs_name> max_mds <old_max_mds>
  73
  74
  75 Upgrading pre-Firefly file systems past Jewel
  76 =============================================
  77
  78 .. tip::
  79
  80     This advice only applies to users with file systems
  81     created using versions of Ceph older than *Firefly* (0.80).
  82     Users creating new file systems may disregard this advice.
  83
  84 Pre-firefly versions of Ceph used a now-deprecated format
  85 for storing CephFS directory objects, called TMAPs.  Support
  86 for reading these in RADOS will be removed after the Jewel
  87 release of Ceph, so for upgrading CephFS users it is important
  88 to ensure that any old directory objects have been converted.
  89
  90 After installing Jewel on all your MDS and OSD servers, and restarting
  91 the services, run the following command:
  92
  93 ::
  94
  95     cephfs-data-scan tmap_upgrade <metadata pool name>
  96
  97 This only needs to be run once, and it is not necessary to
  98 stop any other services while it runs.  The command may take some
  99 time to execute, as it iterates overall objects in your metadata
 100 pool.  It is safe to continue using your file system as normal while
 101 it executes.  If the command aborts for any reason, it is safe
 102 to simply run it again.
 103
 104 If you are upgrading a pre-Firefly CephFS file system to a newer Ceph version
 105 than Jewel, you must first upgrade to Jewel and run the ``tmap_upgrade``
 106 command before completing your upgrade to the latest version.
 107