<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h2 class="title">
      <a name="group-replication-upgrade">
      </a>
      20.8 Upgrading Group Replication
     </h2>
    </div>
   </div>
  </div>
  <div class="toc">
   <dl class="toc">
    <dt>
     <span class="section">
      <a href="group-replication-online-upgrade-combining-versions.html">
       20.8.1 Combining Different Member Versions in a Group
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="group-replication-offline-upgrade.html">
       20.8.2 Group Replication Offline Upgrade
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="group-replication-online-upgrade.html">
       20.8.3 Group Replication Online Upgrade
      </a>
     </span>
    </dt>
   </dl>
  </div>
  <a class="indexterm" name="idm46045131668208">
  </a>
  <p>
   This section explains how to upgrade a Group Replication setup. The
    basic process of upgrading members of a group is the same as
    upgrading stand-alone instances, see
   <a class="xref" href="upgrading.html" title="Chapter 3 Upgrading MySQL">
    Chapter 3,
    <i>
     Upgrading MySQL
    </i>
   </a>
   for
    the actual process of doing upgrade and types available. Choosing
    between an in-place or logical upgrade depends on the amount of data
    stored in the group. Usually an in-place upgrade is faster, and
    therefore is recommended. You should also consult
   <a class="xref" href="replication-upgrade.html" title="19.5.3 Upgrading or Downgrading a Replication Topology">
    Section 19.5.3, “Upgrading or Downgrading a Replication Topology”
   </a>
   .
  </p>
  <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
   <div class="admon-title">
    Note
   </div>
   <p>
    Before MySQL 8.4, a server would not join a group if it was
      running a lower MySQL Server version than the lowest group
      member's version. For example, for a group with S1 (8.0.30), S2
      (8.0.31), and S3 (8.0.32), the joining member needs to be 8.0.30
      or higher. MySQL 8.4 allows all versions within the 8.4 series to
      join. For example, an 8.4.0 server could join a group consisting
      of S1 (8.4.1) and S2 (8.4.2).
   </p>
  </div>
  <p>
   While you are in the process of upgrading an online group, in order
    to maximize availability, you might need to have members with
    different MySQL Server versions running at the same time. Group
    Replication includes compatibility policies that enable you to
    safely combine members running different versions of MySQL in the
    same group during the upgrade procedure. Depending on your group,
    the effects of these policies might affect the order in which you
    should upgrade group members. For details, see
   <a class="xref" href="group-replication-online-upgrade-combining-versions.html" title="20.8.1 Combining Different Member Versions in a Group">
    Section 20.8.1, “Combining Different Member Versions in a Group”
   </a>
   .
  </p>
  <p>
   If your group can be taken fully offline see
   <a class="xref" href="group-replication-offline-upgrade.html" title="20.8.2 Group Replication Offline Upgrade">
    Section 20.8.2, “Group Replication Offline Upgrade”
   </a>
   . If your group
    needs to remain online, as is common with production deployments,
    see
   <a class="xref" href="group-replication-online-upgrade.html" title="20.8.3 Group Replication Online Upgrade">
    Section 20.8.3, “Group Replication Online Upgrade”
   </a>
   for the
    different approaches available for upgrading a group with minimal
    downtime.
  </p>
 </div>
 <br/>
</div>
