<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h4 class="title">
      <a name="performance-schema-replication-asynchronous-connection-failover-managed-table">
      </a>
      29.12.11.9 The replication_asynchronous_connection_failover_managed Table
     </h4>
    </div>
   </div>
  </div>
  <a class="indexterm" name="idm46045071179632">
  </a>
  <a class="indexterm" name="idm46045071178112">
  </a>
  <p>
   This table holds configuration information used by the
          replica's asynchronous connection failover mechanism to
          handle managed groups, including Group Replication topologies.
  </p>
  <p>
   When you add a group member to the source list and define it
          as part of a managed group, the asynchronous connection
          failover mechanism updates the source list to keep it in line
          with membership changes, adding and removing group members
          automatically as they join or leave. When asynchronous
          connection failover is enabled for a group of replicas managed
          by Group Replication, the source lists are broadcast to all
          group members when they join, and also when the lists change.
  </p>
  <p>
   The asynchronous connection failover mechanism fails over the
          connection if another available server on the source list has
          a higher priority (weight) setting. For a managed group, a
          source’s weight is assigned depending on whether it is a
          primary or a secondary server. So assuming that you set up the
          managed group to give a higher weight to a primary and a lower
          weight to a secondary, when the primary changes, the higher
          weight is assigned to the new primary, so the replica changes
          over the connection to it. The asynchronous connection
          failover mechanism additionally changes connection if the
          currently connected managed source server leaves the managed
          group, or is no longer in the majority in the managed group.
          For more information, see
   <a class="xref" href="replication-asynchronous-connection-failover.html" title="19.4.9 Switching Sources and Replicas with Asynchronous Connection Failover">
    Section 19.4.9, “Switching Sources and Replicas with Asynchronous Connection Failover”
   </a>
   .
  </p>
  <p>
   The
   <a class="link" href="performance-schema-replication-asynchronous-connection-failover-managed-table.html" title="29.12.11.9 The replication_asynchronous_connection_failover_managed Table">
    <code class="literal">
     replication_asynchronous_connection_failover_managed
    </code>
   </a>
   table has these columns:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <code class="literal">
       CHANNEL_NAME
      </code>
     </p>
     <p>
      The replication channel where the servers for this managed
              group operate.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       MANAGED_NAME
      </code>
     </p>
     <p>
      The identifier for the managed group. For the
      <code class="literal">
       GroupReplication
      </code>
      managed service, the
              identifier is the value of the
      <a class="link" href="group-replication-system-variables.html#sysvar_group_replication_group_name">
       <code class="literal">
        group_replication_group_name
       </code>
      </a>
      system variable.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       MANAGED_TYPE
      </code>
     </p>
     <p>
      The type of managed service that the asynchronous
              connection failover mechanism provides for this group. The
              only value currently available is
      <code class="literal">
       GroupReplication
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       CONFIGURATION
      </code>
     </p>
     <p>
      The configuration information for this managed group. For
              the
      <code class="literal">
       GroupReplication
      </code>
      managed service,
              the configuration shows the weights assigned to the
              group's primary server and to the group's
              secondary servers. For example:
      <code class="literal">
       {"Primary_weight": 80, "Secondary_weight":
              60}
      </code>
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         <code class="literal">
          Primary_weight
         </code>
         : Integer between 0
                  and 100. Default value is 80.
        </p>
       </li>
       <li class="listitem">
        <p>
         <code class="literal">
          Secondary_weight
         </code>
         : Integer between 0
                  and 100. Default value is 60.
        </p>
       </li>
      </ul>
     </div>
    </li>
   </ul>
  </div>
  <p>
   The
   <a class="link" href="performance-schema-replication-asynchronous-connection-failover-managed-table.html" title="29.12.11.9 The replication_asynchronous_connection_failover_managed Table">
    <code class="literal">
     replication_asynchronous_connection_failover_managed
    </code>
   </a>
   table has these indexes:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      Primary key on (
      <code class="literal">
       CHANNEL_NAME,
              MANAGED_NAME
      </code>
      )
     </p>
    </li>
   </ul>
  </div>
  <p>
   <a class="link" href="truncate-table.html" title="15.1.37 TRUNCATE TABLE Statement">
    <code class="literal">
     TRUNCATE TABLE
    </code>
   </a>
   is not permitted
          for the
   <a class="link" href="performance-schema-replication-asynchronous-connection-failover-managed-table.html" title="29.12.11.9 The replication_asynchronous_connection_failover_managed Table">
    <code class="literal">
     replication_asynchronous_connection_failover_managed
    </code>
   </a>
   table.
  </p>
 </div>
 <br/>
</div>
