anchor.diff:    server as unavailable. The cluster will otherwise operate fine without the
     tablet server. To completely remove it from the cluster so `ksck` shows the
     cluster as completely healthy, restart the masters. In the case of a single
  -  master, this will cause cluster downtime. With multimaster, restart the
  +  master, this will cause cluster downtime. With multi-master, restart the
     masters in sequence to avoid cluster downtime.
   
   WARNING: Do not shut down multiple tablet servers at once. To remove multiple
  
positive.code:   workflow will refer to this master as the "reference" master.
  
  . Choose an unused machine in the cluster where the new master will live. The master generates very
    little load so it can be colocated with other data services or load-generating processes, though
    not with another Kudu master from the same configuration. The rest of this workflow will refer to
    this master as the "replacement" master.
  
  . Perform the following preparatory steps for the replacement master:
  * Ensure Kudu is installed on the machine, either via system packages (in which case the `kudu` and
  
negative.code: the migration section for updating HMS.
  +
  . Perform the following preparatory steps for each new master:
  * Choose an unused machine in the cluster. The master generates very little load
    so it can be collocated with other data services or load-generating processes,
    though not with another Kudu master from the same configuration.
  * Ensure Kudu is installed on the machine, either via system packages (in which case the `kudu` and
    `kudu-master` packages should be installed), or via some other means.
  * Choose and record the directory where the master's data will live.
  