<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h4 class="title">
      <a name="show-replica-status">
      </a>
      15.7.7.35 SHOW REPLICA STATUS Statement
     </h4>
    </div>
   </div>
  </div>
  <a class="indexterm" name="idm46045169681904">
  </a>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting one-line language-sql"><div class="docs-select-all right" id="sa74035616"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-sql"><span class="token keyword">SHOW</span> <span class="token keyword">REPLICA</span> <span class="token keyword">STATUS</span> <span class="token punctuation">[</span><span class="token keyword">FOR</span> <span class="token keyword">CHANNEL</span> <span class="token keyword"><em class="replaceable">channel</em></span><span class="token punctuation">]</span></code></pre>
  </div>
  <p>
   This statement provides status information on essential
        parameters of the replica threads. The statement requires the
   <a class="link" href="privileges-provided.html#priv_replication-client">
    <code class="literal">
     REPLICATION CLIENT
    </code>
   </a>
   privilege (or
        the deprecated
   <a class="link" href="privileges-provided.html#priv_super">
    <code class="literal">
     SUPER
    </code>
   </a>
   privilege).
  </p>
  <p>
   <code class="literal">
    SHOW REPLICA STATUS
   </code>
   is nonblocking. When run
        concurrently with
   <a class="link" href="stop-replica.html" title="15.4.2.5 STOP REPLICA Statement">
    <code class="literal">
     STOP
        REPLICA
    </code>
   </a>
   ,
   <code class="literal">
    SHOW REPLICA STATUS
   </code>
   returns without waiting for
   <a class="link" href="stop-replica.html" title="15.4.2.5 STOP REPLICA Statement">
    <code class="literal">
     STOP
        REPLICA
    </code>
   </a>
   to finish shutting down the replication SQL
        (applier) thread or replication I/O (receiver) thread (or both).
        This permits use in monitoring and other applications where
        getting an immediate response from
   <code class="literal">
    SHOW REPLICA
        STATUS
   </code>
   is more important than ensuring that it
        returned the latest data.
  </p>
  <p>
   If you issue this statement using the
   <a class="link" href="mysql.html" title="6.5.1 mysql — The MySQL Command-Line Client">
    <span class="command">
     <strong>
      mysql
     </strong>
    </span>
   </a>
   client, you can use a
   <code class="literal">
    \G
   </code>
   statement terminator
        rather than a semicolon to obtain a more readable vertical
        layout:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting language-sql"><div class="docs-select-all right" id="sa89074407"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-sql"><span class="token prompt">mysql&gt;</span> <span class="token keyword">SHOW</span> <span class="token keyword">REPLICA</span> <span class="token keyword">STATUS</span>\G
<span class="token output"><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span> 1. row <span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span><span class="token punctuation">*</span>
             Replica_IO_State<span class="token punctuation">:</span> Waiting for source to send event
                  Source_Host<span class="token punctuation">:</span> 127.0.0.1
                  Source_User<span class="token punctuation">:</span> root
                  Source_Port<span class="token punctuation">:</span> 13000
                Connect_Retry<span class="token punctuation">:</span> 1
              Source_Log_File<span class="token punctuation">:</span> master-bin.000001
          Read_Source_Log_Pos<span class="token punctuation">:</span> 927
               Relay_Log_File<span class="token punctuation">:</span> slave-relay-bin.000002
                Relay_Log_Pos<span class="token punctuation">:</span> 1145
        Relay_Source_Log_File<span class="token punctuation">:</span> master-bin.000001
           Replica_IO_Running<span class="token punctuation">:</span> Yes
          Replica_SQL_Running<span class="token punctuation">:</span> Yes
              Replicate_Do_DB<span class="token punctuation">:</span>
          Replicate_Ignore_DB<span class="token punctuation">:</span>
           Replicate_Do_Table<span class="token punctuation">:</span>
       Replicate_Ignore_Table<span class="token punctuation">:</span>
      Replicate_Wild_Do_Table<span class="token punctuation">:</span>
  Replicate_Wild_Ignore_Table<span class="token punctuation">:</span>
                   Last_Errno<span class="token punctuation">:</span> 0
                   Last_Error<span class="token punctuation">:</span>
                 Skip_Counter<span class="token punctuation">:</span> 0
          Exec_Source_Log_Pos<span class="token punctuation">:</span> 927
              Relay_Log_Space<span class="token punctuation">:</span> 1355
              Until_Condition<span class="token punctuation">:</span> None
               Until_Log_File<span class="token punctuation">:</span>
                Until_Log_Pos<span class="token punctuation">:</span> 0
           Source_SSL_Allowed<span class="token punctuation">:</span> No
           Source_SSL_CA_File<span class="token punctuation">:</span>
           Source_SSL_CA_Path<span class="token punctuation">:</span>
              Source_SSL_Cert<span class="token punctuation">:</span>
            Source_SSL_Cipher<span class="token punctuation">:</span>
               Source_SSL_Key<span class="token punctuation">:</span>
        Seconds_Behind_Source<span class="token punctuation">:</span> 0
Source_SSL_Verify_Server_Cert<span class="token punctuation">:</span> No
                Last_IO_Errno<span class="token punctuation">:</span> 0
                Last_IO_Error<span class="token punctuation">:</span>
               Last_SQL_Errno<span class="token punctuation">:</span> 0
               Last_SQL_Error<span class="token punctuation">:</span>
  Replicate_Ignore_Server_Ids<span class="token punctuation">:</span>
             Source_Server_Id<span class="token punctuation">:</span> 1
                  Source_UUID<span class="token punctuation">:</span> 73f86016-978b-11ee-ade5-8d2a2a562feb
             Source_Info_File<span class="token punctuation">:</span> mysql.slave_master_info
                    SQL_Delay<span class="token punctuation">:</span> 0
          SQL_Remaining_Delay<span class="token punctuation">:</span> NULL
    Replica_SQL_Running_State<span class="token punctuation">:</span> Replica has read all relay log; waiting for more updates
           Source_Retry_Count<span class="token punctuation">:</span> 10
                  Source_Bind<span class="token punctuation">:</span>
      Last_IO_Error_Timestamp<span class="token punctuation">:</span>
     Last_SQL_Error_Timestamp<span class="token punctuation">:</span>
               Source_SSL_Crl<span class="token punctuation">:</span>
           Source_SSL_Crlpath<span class="token punctuation">:</span>
           Retrieved_Gtid_Set<span class="token punctuation">:</span> 73f86016-978b-11ee-ade5-8d2a2a562feb<span class="token punctuation">:</span>1-3
            Executed_Gtid_Set<span class="token punctuation">:</span> 73f86016-978b-11ee-ade5-8d2a2a562feb<span class="token punctuation">:</span>1-3
                Auto_Position<span class="token punctuation">:</span> 1
         Replicate_Rewrite_DB<span class="token punctuation">:</span>
                 Channel_Name<span class="token punctuation">:</span>
           Source_TLS_Version<span class="token punctuation">:</span>
       Source_public_key_path<span class="token punctuation">:</span>
        Get_Source_public_key<span class="token punctuation">:</span> 0
            Network_Namespace<span class="token punctuation">:</span></span></code></pre>
  </div>
  <p>
   The Performance Schema provides tables that expose replication
        information. This is similar to the information available from
        the
   <a class="link" href="show-replica-status.html" title="15.7.7.35 SHOW REPLICA STATUS Statement">
    <code class="literal">
     SHOW REPLICA STATUS
    </code>
   </a>
   statement, but represented in table form. For details, see
   <a class="xref" href="performance-schema-replication-tables.html" title="29.12.11 Performance Schema Replication Tables">
    Section 29.12.11, “Performance Schema Replication Tables”
   </a>
   .
  </p>
  <p>
   You can set the
   <code class="literal">
    GTID_ONLY
   </code>
   option for the
   <a class="link" href="change-replication-source-to.html" title="15.4.2.2 CHANGE REPLICATION SOURCE TO Statement">
    <code class="literal">
     CHANGE REPLICATION SOURCE TO
    </code>
   </a>
   statement to stop a replication channel from persisting file
        names and file positions in the replication metadata
        repositories. With this setting, file positions for the source
        binary log file and the relay log file are tracked in memory.
        The
   <a class="link" href="show-replica-status.html" title="15.7.7.35 SHOW REPLICA STATUS Statement">
    <code class="literal">
     SHOW REPLICA STATUS
    </code>
   </a>
   statement
        still displays file positions in normal use. However, because
        the file positions are not being regularly updated in the
        connection metadata repository and the applier metadata
        repository except in a few situations, they are likely to be out
        of date if the server is restarted.
  </p>
  <p>
   For a replication channel with the
   <code class="literal">
    GTID_ONLY
   </code>
   setting after a server start, the read and applied file
        positions for the source binary log file
        (
   <code class="literal">
    Read_Source_Log_Pos
   </code>
   and
   <code class="literal">
    Exec_Source_Log_Pos
   </code>
   ) are set to zero, and the
        file names (
   <code class="literal">
    Source_Log_File
   </code>
   and
   <code class="literal">
    Relay_Source_Log_File
   </code>
   ) are set to
   <code class="literal">
    INVALID
   </code>
   . The relay log file name
        (
   <code class="literal">
    Relay_Log_File
   </code>
   ) is set according to the
        relay_log_recovery setting, either a new file that was created
        at server start or the first relay log file present. The file
        position (
   <code class="literal">
    Relay_Log_Pos
   </code>
   ) is set to position
        4, and GTID auto-skip is used to skip any transactions in the
        file that were already applied.
  </p>
  <p>
   When the receiver thread contacts the source and gets valid
        position information, the read position
        (
   <code class="literal">
    Read_Source_Log_Pos
   </code>
   ) and file name
        (
   <code class="literal">
    Source_Log_File
   </code>
   ) are updated with the
        correct data and become valid. When the applier thread applies a
        transaction from the source, or skips an already executed
        transaction, the executed position
        (
   <code class="literal">
    Exec_Source_Log_Pos
   </code>
   ) and file name
        (
   <code class="literal">
    Relay_Source_Log_File
   </code>
   ) are updated with the
        correct data and become valid. The relay log file position
        (
   <code class="literal">
    Relay_Log_Pos
   </code>
   ) is also updated at that time.
  </p>
  <p>
   The following list describes the fields returned by
   <a class="link" href="show-replica-status.html" title="15.7.7.35 SHOW REPLICA STATUS Statement">
    <code class="literal">
     SHOW
        REPLICA STATUS
    </code>
   </a>
   . For additional information about
        interpreting their meanings, see
   <a class="xref" href="replication-administration-status.html" title="19.1.7.1 Checking Replication Status">
    Section 19.1.7.1, “Checking Replication Status”
   </a>
   .
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <code class="literal">
       Replica_IO_State
      </code>
     </p>
     <p>
      A copy of the
      <code class="literal">
       State
      </code>
      field of the
      <a class="link" href="show-processlist.html" title="15.7.7.31 SHOW PROCESSLIST Statement">
       <code class="literal">
        SHOW PROCESSLIST
       </code>
      </a>
      output for
            the replica I/O (receiver) thread. This tells you what the
            thread is doing: trying to connect to the source, waiting
            for events from the source, reconnecting to the source, and
            so on. For a listing of possible states, see
      <a class="xref" href="replica-io-thread-states.html" title="10.14.5 Replication I/O (Receiver) Thread States">
       Section 10.14.5, “Replication I/O (Receiver) Thread States”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Source_Host
      </code>
     </p>
     <p>
      The source host that the replica is connected to.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Source_User
      </code>
     </p>
     <p>
      The user name of the account used to connect to the source.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Source_Port
      </code>
     </p>
     <p>
      The port used to connect to the source.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Connect_Retry
      </code>
     </p>
     <p>
      The number of seconds between connect retries (default 60).
            This can be set with a
      <a class="link" href="change-replication-source-to.html" title="15.4.2.2 CHANGE REPLICATION SOURCE TO Statement">
       <code class="literal">
        CHANGE
            REPLICATION SOURCE TO
       </code>
      </a>
      statement.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Source_Log_File
      </code>
     </p>
     <p>
      The name of the source binary log file from which the I/O
            (receiver) thread is currently reading. This is set to
      <code class="literal">
       INVALID
      </code>
      for a replication channel with
            the
      <code class="literal">
       GTID_ONLY
      </code>
      setting after a server
            start. It will be updated when the replica contacts the
            source.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Read_Source_Log_Pos
      </code>
     </p>
     <p>
      The position in the current source binary log file up to
            which the I/O (receiver) thread has read. This is set to
            zero for a replication channel with the
      <code class="literal">
       GTID_ONLY
      </code>
      setting after a server start.
            It will be updated when the replica contacts the source.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Relay_Log_File
      </code>
     </p>
     <p>
      The name of the relay log file from which the SQL (applier)
            thread is currently reading and executing.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Relay_Log_Pos
      </code>
     </p>
     <p>
      The position in the current relay log file up to which the
            SQL (applier) thread has read and executed.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Relay_Source_Log_File
      </code>
     </p>
     <p>
      The name of the source binary log file containing the most
            recent event executed by the SQL (applier) thread. This is
            set to
      <code class="literal">
       INVALID
      </code>
      for a replication channel
            with the
      <code class="literal">
       GTID_ONLY
      </code>
      setting after a server
            start. It will be updated when a transaction is executed or
            skipped.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Replica_IO_Running
      </code>
     </p>
     <p>
      Whether the replication I/O (receiver) thread is started and
            has connected successfully to the source. Internally, the
            state of this thread is represented by one of the following
            three values:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         <b>
          MYSQL_REPLICA_NOT_RUN.
         </b>
         The replication I/O (receiver) thread is not running.
                  For this state,
         <code class="literal">
          Replica_IO_Running
         </code>
         is
         <code class="literal">
          No
         </code>
         .
        </p>
       </li>
       <li class="listitem">
        <p>
         <b>
          MYSQL_REPLICA_RUN_NOT_CONNECT.
         </b>
         The replication I/O (receiver) thread is running, but
                  is not connected to a replication source. For this
                  state,
         <code class="literal">
          Replica_IO_Running
         </code>
         is
         <code class="literal">
          Connecting
         </code>
         .
        </p>
       </li>
       <li class="listitem">
        <p>
         <b>
          MYSQL_REPLICA_RUN_CONNECT.
         </b>
         The replication I/O (receiver) thread is running, and
                  is connected to a replication source. For this state,
         <code class="literal">
          Replica_IO_Running
         </code>
         is
         <code class="literal">
          Yes
         </code>
         .
        </p>
       </li>
      </ul>
     </div>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Replica_SQL_Running
      </code>
     </p>
     <p>
      Whether the replication SQL (applier) thread is started.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Replicate_Do_DB
      </code>
      ,
      <code class="literal">
       Replicate_Ignore_DB
      </code>
     </p>
     <p>
      The names of any databases that were specified with the
      <a class="link" href="replication-options-replica.html#option_mysqld_replicate-do-db">
       <code class="option">
        --replicate-do-db
       </code>
      </a>
      and
      <a class="link" href="replication-options-replica.html#option_mysqld_replicate-ignore-db">
       <code class="option">
        --replicate-ignore-db
       </code>
      </a>
      options, or the
      <a class="link" href="change-replication-filter.html" title="15.4.2.1 CHANGE REPLICATION FILTER Statement">
       <code class="literal">
        CHANGE REPLICATION
            FILTER
       </code>
      </a>
      statement. If the
      <code class="literal">
       FOR
            CHANNEL
      </code>
      clause was used, the channel specific
            replication filters are shown. Otherwise, the replication
            filters for every replication channel are shown.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Replicate_Do_Table
      </code>
      ,
      <code class="literal">
       Replicate_Ignore_Table
      </code>
      ,
      <code class="literal">
       Replicate_Wild_Do_Table
      </code>
      ,
      <code class="literal">
       Replicate_Wild_Ignore_Table
      </code>
     </p>
     <p>
      The names of any tables that were specified with the
      <a class="link" href="replication-options-replica.html#option_mysqld_replicate-do-table">
       <code class="option">
        --replicate-do-table
       </code>
      </a>
      ,
      <a class="link" href="replication-options-replica.html#option_mysqld_replicate-ignore-table">
       <code class="option">
        --replicate-ignore-table
       </code>
      </a>
      ,
      <a class="link" href="replication-options-replica.html#option_mysqld_replicate-wild-do-table">
       <code class="option">
        --replicate-wild-do-table
       </code>
      </a>
      ,
            and
      <a class="link" href="replication-options-replica.html#option_mysqld_replicate-wild-ignore-table">
       <code class="option">
        --replicate-wild-ignore-table
       </code>
      </a>
      options, or the
      <a class="link" href="change-replication-filter.html" title="15.4.2.1 CHANGE REPLICATION FILTER Statement">
       <code class="literal">
        CHANGE REPLICATION
            FILTER
       </code>
      </a>
      statement. If the
      <code class="literal">
       FOR
            CHANNEL
      </code>
      clause was used, the channel specific
            replication filters are shown. Otherwise, the replication
            filters for every replication channel are shown.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Last_Errno
      </code>
      ,
      <code class="literal">
       Last_Error
      </code>
     </p>
     <p>
      These columns are aliases for
      <code class="literal">
       Last_SQL_Errno
      </code>
      and
      <code class="literal">
       Last_SQL_Error
      </code>
      .
     </p>
     <p>
      Issuing
      <a class="link" href="reset-binary-logs-and-gtids.html" title="15.4.1.2 RESET BINARY LOGS AND GTIDS Statement">
       <code class="literal">
        RESET BINARY LOGS AND
            GTIDS
       </code>
      </a>
      or
      <a class="link" href="reset-replica.html" title="15.4.2.3 RESET REPLICA Statement">
       <code class="literal">
        RESET
            REPLICA
       </code>
      </a>
      resets the values shown in these columns.
     </p>
     <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
      <div class="admon-title">
       Note
      </div>
      <p>
       When the replication SQL thread receives an error, it
              reports the error first, then stops the SQL thread. This
              means that there is a small window of time during which
       <code class="literal">
        SHOW REPLICA STATUS
       </code>
       shows a nonzero
              value for
       <code class="literal">
        Last_SQL_Errno
       </code>
       even though
       <code class="literal">
        Replica_SQL_Running
       </code>
       still displays
       <code class="literal">
        Yes
       </code>
       .
      </p>
     </div>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Skip_Counter
      </code>
     </p>
     <p>
      The current value of the
      <a class="link" href="replication-options-replica.html#sysvar_sql_replica_skip_counter">
       <code class="literal">
        sql_replica_skip_counter
       </code>
      </a>
      system variable.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Exec_Source_Log_Pos
      </code>
     </p>
     <p>
      The position in the current source binary log file to which
            the replication SQL thread has read and executed, marking
            the start of the next transaction or event to be processed.
            This is set to zero for a replication channel with the
      <code class="literal">
       GTID_ONLY
      </code>
      setting after a server start.
            It will be updated when a transaction is executed or
            skipped.
     </p>
     <p>
      You can use this value with the
      <a class="link" href="change-replication-source-to.html" title="15.4.2.2 CHANGE REPLICATION SOURCE TO Statement">
       <code class="literal">
        CHANGE
            REPLICATION SOURCE TO
       </code>
      </a>
      statement's
      <code class="literal">
       SOURCE_LOG_POS
      </code>
      option when starting a new
            replica from an existing replica, so that the new replica
            reads from this point. The coordinates given by
            (
      <code class="literal">
       Relay_Source_Log_File
      </code>
      ,
      <code class="literal">
       Exec_Source_Log_Pos
      </code>
      ) in the source's
            binary log correspond to the coordinates given by
            (
      <code class="literal">
       Relay_Log_File
      </code>
      ,
      <code class="literal">
       Relay_Log_Pos
      </code>
      ) in the relay log.
     </p>
     <p>
      Inconsistencies in the sequence of transactions from the
            relay log which have been executed can cause this value to
            be a
      <span class="quote">
       “
       <span class="quote">
        low-water mark
       </span>
       ”
      </span>
      . In other words,
            transactions appearing before the position are guaranteed to
            have committed, but transactions after the position may have
            committed or not. If these gaps need to be corrected, use
      <a class="link" href="start-replica.html" title="15.4.2.4 START REPLICA Statement">
       <code class="literal">
        START REPLICA
            UNTIL SQL_AFTER_MTS_GAPS
       </code>
      </a>
      . See
      <a class="xref" href="replication-features-transaction-inconsistencies.html" title="19.5.1.34 Replication and Transaction Inconsistencies">
       Section 19.5.1.34, “Replication and Transaction Inconsistencies”
      </a>
      for more information.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Relay_Log_Space
      </code>
     </p>
     <p>
      The total combined size of all existing relay log files.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Until_Condition
      </code>
      ,
      <code class="literal">
       Until_Log_File
      </code>
      ,
      <code class="literal">
       Until_Log_Pos
      </code>
     </p>
     <p>
      The values specified in the
      <code class="literal">
       UNTIL
      </code>
      clause
            of the
      <a class="link" href="start-replica.html" title="15.4.2.4 START REPLICA Statement">
       <code class="literal">
        START
            REPLICA
       </code>
      </a>
      statement.
     </p>
     <p>
      <code class="literal">
       Until_Condition
      </code>
      has these values:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         <code class="literal">
          None
         </code>
         if no
         <code class="literal">
          UNTIL
         </code>
         clause was specified.
        </p>
       </li>
       <li class="listitem">
        <p>
         <code class="literal">
          Source
         </code>
         if the replica is reading
                until a given position in the source's binary log.
        </p>
       </li>
       <li class="listitem">
        <p>
         <code class="literal">
          Relay
         </code>
         if the replica is reading until
                a given position in its relay log.
        </p>
       </li>
       <li class="listitem">
        <p>
         <code class="literal">
          SQL_BEFORE_GTIDS
         </code>
         if the replication
                SQL thread is processing transactions until it has
                reached the first transaction whose GTID is listed in
                the
         <code class="literal">
          gtid_set
         </code>
         .
        </p>
       </li>
       <li class="listitem">
        <p>
         <code class="literal">
          SQL_AFTER_GTIDS
         </code>
         if the replication
                threads are processing all transactions until the last
                transaction in the
         <code class="literal">
          gtid_set
         </code>
         has been
                processed by both threads.
        </p>
       </li>
       <li class="listitem">
        <p>
         <code class="literal">
          SQL_AFTER_MTS_GAPS
         </code>
         if a multithreaded
                replica's SQL threads are running until no more gaps are
                found in the relay log.
        </p>
       </li>
      </ul>
     </div>
     <p>
      <code class="literal">
       Until_Log_File
      </code>
      and
      <code class="literal">
       Until_Log_Pos
      </code>
      indicate the log file name
            and position that define the coordinates at which the
            replication SQL thread stops executing.
     </p>
     <p>
      For more information on
      <code class="literal">
       UNTIL
      </code>
      clauses,
            see
      <a class="xref" href="start-replica.html" title="15.4.2.4 START REPLICA Statement">
       Section 15.4.2.4, “START REPLICA Statement”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Source_SSL_Allowed
      </code>
      ,
      <code class="literal">
       Source_SSL_CA_File
      </code>
      ,
      <code class="literal">
       Source_SSL_CA_Path
      </code>
      ,
      <code class="literal">
       Source_SSL_Cert
      </code>
      ,
      <code class="literal">
       Source_SSL_Cipher
      </code>
      ,
      <code class="literal">
       Source_SSL_CRL_File
      </code>
      ,
      <code class="literal">
       Source_SSL_CRL_Path
      </code>
      ,
      <code class="literal">
       Source_SSL_Key
      </code>
      ,
      <code class="literal">
       Source_SSL_Verify_Server_Cert
      </code>
     </p>
     <p>
      These fields show the SSL parameters used by the replica to
            connect to the source, if any.
     </p>
     <p>
      <code class="literal">
       Source_SSL_Allowed
      </code>
      has these values:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         <code class="literal">
          Yes
         </code>
         if an SSL connection to the
                source is permitted.
        </p>
       </li>
       <li class="listitem">
        <p>
         <code class="literal">
          No
         </code>
         if an SSL connection to the source
                is not permitted.
        </p>
       </li>
       <li class="listitem">
        <p>
         <code class="literal">
          Ignored
         </code>
         if an SSL connection is
                permitted but the replica server does not have SSL
                support enabled.
        </p>
       </li>
      </ul>
     </div>
     <p>
      The values of the other SSL-related fields correspond to the
            values of the
      <code class="literal">
       SOURCE_SSL_*
      </code>
      options of the
      <a class="link" href="change-replication-source-to.html" title="15.4.2.2 CHANGE REPLICATION SOURCE TO Statement">
       <code class="literal">
        CHANGE REPLICATION SOURCE TO
       </code>
      </a>
      statement.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Seconds_Behind_Source
      </code>
     </p>
     <p>
      This field is an indication of how
      <span class="quote">
       “
       <span class="quote">
        late
       </span>
       ”
      </span>
      the
            replica is:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         When the replica is actively processing updates, this
                field shows the difference between the current timestamp
                on the replica and the original timestamp logged on the
                source for the event currently being processed on the
                replica.
        </p>
       </li>
       <li class="listitem">
        <p>
         When no event is currently being processed on the
                replica, this value is 0.
        </p>
       </li>
      </ul>
     </div>
     <p>
      In essence, this field measures the time difference in
            seconds between the replication SQL (applier) thread and the
            replication I/O (receiver) thread. If the network connection
            between source and replica is fast, the replication receiver
            thread is very close to the source, so this field is a good
            approximation of how late the replication applier thread is
            compared to the source. If the network is slow, this is
      <span class="emphasis">
       <em>
        not
       </em>
      </span>
      a good approximation; the
            replication applier thread may quite often be caught up with
            the slow-reading replication receiver thread, so
      <code class="literal">
       Seconds_Behind_Source
      </code>
      often shows a value
            of 0, even if the replication receiver thread is late
            compared to the source. In other words,
      <span class="emphasis">
       <em>
        this
            column is useful only for fast networks
       </em>
      </span>
      .
     </p>
     <p>
      This time difference computation works even if the source
            and replica do not have identical clock times, provided that
            the difference, computed when the replica receiver thread
            starts, remains constant from then on. Any changes,
            including NTP updates, can lead to clock skews that can make
            calculation of
      <code class="literal">
       Seconds_Behind_Source
      </code>
      less
            reliable.
     </p>
     <p>
      In MySQL 8.4, this field is
      <code class="literal">
       NULL
      </code>
      (undefined or unknown) if the
            replication applier thread is not running, or if the applier
            thread has consumed all of the relay log and the replication
            receiver thread is not running. (In older versions of MySQL,
            this field was
      <code class="literal">
       NULL
      </code>
      if the replication
            applier thread or the replication receiver thread was not
            running or was not connected to the source.) If the
            replication receiver thread is running but the relay log is
            exhausted,
      <code class="literal">
       Seconds_Behind_Source
      </code>
      is set
            to 0.
     </p>
     <p>
      The value of
      <code class="literal">
       Seconds_Behind_Source
      </code>
      is
            based on the timestamps stored in events, which are
            preserved through replication. This means that if a source
            M1 is itself a replica of M0, any event from M1's binary log
            that originates from M0's binary log has M0's timestamp for
            that event. This enables MySQL to replicate
      <a class="link" href="datetime.html" title="13.2.2 The DATE, DATETIME, and TIMESTAMP Types">
       <code class="literal">
        TIMESTAMP
       </code>
      </a>
      successfully.
            However, the problem for
      <code class="literal">
       Seconds_Behind_Source
      </code>
      is that if M1 also
            receives direct updates from clients, the
      <code class="literal">
       Seconds_Behind_Source
      </code>
      value randomly
            fluctuates because sometimes the last event from M1
            originates from M0 and sometimes is the result of a direct
            update on M1.
     </p>
     <p>
      When using a multithreaded replica, you should keep in mind
            that this value is based on
      <code class="literal">
       Exec_Source_Log_Pos
      </code>
      , and so may not
            reflect the position of the most recently committed
            transaction.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Last_IO_Errno
      </code>
      ,
      <code class="literal">
       Last_IO_Error
      </code>
     </p>
     <p>
      The error number and error message of the most recent error
            that caused the replication I/O (receiver) thread to stop.
            An error number of 0 and message of the empty string mean
      <span class="quote">
       “
       <span class="quote">
        no error.
       </span>
       ”
      </span>
      If the
      <code class="literal">
       Last_IO_Error
      </code>
      value is not empty, the
            error values also appear in the replica's error log.
     </p>
     <p>
      I/O error information includes a timestamp showing when the
            most recent I/O (receiver)thread error occurred. This
            timestamp uses the format
      <em class="replaceable">
       <code>
        YYMMDD
            hh:mm:ss
       </code>
      </em>
      , and appears in the
      <code class="literal">
       Last_IO_Error_Timestamp
      </code>
      column.
     </p>
     <p>
      Issuing
      <a class="link" href="reset-binary-logs-and-gtids.html" title="15.4.1.2 RESET BINARY LOGS AND GTIDS Statement">
       <code class="literal">
        RESET BINARY LOGS AND
            GTIDS
       </code>
      </a>
      or
      <a class="link" href="reset-replica.html" title="15.4.2.3 RESET REPLICA Statement">
       <code class="literal">
        RESET
            REPLICA
       </code>
      </a>
      resets the values shown in these columns.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Last_SQL_Errno
      </code>
      ,
      <code class="literal">
       Last_SQL_Error
      </code>
     </p>
     <p>
      The error number and error message of the most recent error
            that caused the replication SQL (applier) thread to stop. An
            error number of 0 and message of the empty string mean
      <span class="quote">
       “
       <span class="quote">
        no error.
       </span>
       ”
      </span>
      If the
      <code class="literal">
       Last_SQL_Error
      </code>
      value is not empty, the
            error values also appear in the replica's error log.
     </p>
     <p>
      If the replica is multithreaded, the replication SQL thread
            is the coordinator for worker threads. In this case, the
      <code class="literal">
       Last_SQL_Error
      </code>
      field shows exactly what
            the
      <code class="literal">
       Last_Error_Message
      </code>
      column in the
            Performance Schema
      <a class="link" href="performance-schema-replication-applier-status-by-coordinator-table.html" title="29.12.11.6 The replication_applier_status_by_coordinator Table">
       <code class="literal">
        replication_applier_status_by_coordinator
       </code>
      </a>
      table shows. The field value is modified to suggest that
            there may be more failures in the other worker threads which
            can be seen in the
      <a class="link" href="performance-schema-replication-applier-status-by-worker-table.html" title="29.12.11.7 The replication_applier_status_by_worker Table">
       <code class="literal">
        replication_applier_status_by_worker
       </code>
      </a>
      table that shows each worker thread's status. If that table
            is not available, the replica error log can be used. The log
            or the
      <a class="link" href="performance-schema-replication-applier-status-by-worker-table.html" title="29.12.11.7 The replication_applier_status_by_worker Table">
       <code class="literal">
        replication_applier_status_by_worker
       </code>
      </a>
      table should also be used to learn more about the failure
            shown by
      <a class="link" href="show-replica-status.html" title="15.7.7.35 SHOW REPLICA STATUS Statement">
       <code class="literal">
        SHOW
            REPLICA STATUS
       </code>
      </a>
      or the coordinator table.
     </p>
     <p>
      SQL error information includes a timestamp showing when the
            most recent SQL (applier) thread error occurred. This
            timestamp uses the format
      <em class="replaceable">
       <code>
        YYMMDD
            hh:mm:ss
       </code>
      </em>
      , and appears in the
      <code class="literal">
       Last_SQL_Error_Timestamp
      </code>
      column.
     </p>
     <p>
      Issuing
      <a class="link" href="reset-binary-logs-and-gtids.html" title="15.4.1.2 RESET BINARY LOGS AND GTIDS Statement">
       <code class="literal">
        RESET BINARY LOGS AND
            GTIDS
       </code>
      </a>
      or
      <a class="link" href="reset-replica.html" title="15.4.2.3 RESET REPLICA Statement">
       <code class="literal">
        RESET
            REPLICA
       </code>
      </a>
      resets the values shown in these columns.
     </p>
     <p>
      In MySQL 8.4, all error codes and messages
            displayed in the
      <code class="literal">
       Last_SQL_Errno
      </code>
      and
      <code class="literal">
       Last_SQL_Error
      </code>
      columns correspond to
            error values listed in
      <a class="ulink" href="/doc/mysql-errors/8.4/en/server-error-reference.html" target="_top">
       Server Error Message Reference
      </a>
      . This was not
            always true in previous versions. (Bug #11760365, Bug
            #52768)
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Replicate_Ignore_Server_Ids
      </code>
     </p>
     <p>
      Any server IDs that have been specified using the
      <code class="literal">
       IGNORE_SERVER_IDS
      </code>
      option of the
      <a class="link" href="change-replication-source-to.html" title="15.4.2.2 CHANGE REPLICATION SOURCE TO Statement">
       <code class="literal">
        CHANGE REPLICATION SOURCE TO
       </code>
      </a>
      statement, so that the replica ignores events from these
            servers. This option is used in a circular or other
            multi-source replication setup when one of the servers is
            removed. If any server IDs have been set in this way, a
            comma-delimited list of one or more numbers is shown. If no
            server IDs have been set, the field is blank.
     </p>
     <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
      <div class="admon-title">
       Note
      </div>
      <p>
       The
       <code class="literal">
        Ignored_server_ids
       </code>
       value in the
       <code class="literal">
        slave_master_info
       </code>
       table also shows the
              server IDs to be ignored, but as a space-delimited list,
              preceded by the total number of server IDs to be ignored.
              For example, if a
       <a class="link" href="change-replication-source-to.html" title="15.4.2.2 CHANGE REPLICATION SOURCE TO Statement">
        <code class="literal">
         CHANGE REPLICATION
              SOURCE TO
        </code>
       </a>
       statement containing the
       <code class="literal">
        IGNORE_SERVER_IDS = (2,6,9)
       </code>
       option has
              been issued to tell a replica to ignore sources having the
              server ID 2, 6, or 9, that information appears as shown
              here:
      </p>
      <div class="copytoclipboard-wrapper">
       <pre class="programlisting one-line language-none"><div class="docs-select-all right" id="sa35760093"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-none">	Replicate_Ignore_Server_Ids: 2, 6, 9</code></pre>
      </div>
      <div class="copytoclipboard-wrapper">
       <pre class="programlisting one-line language-none"><div class="docs-select-all right" id="sa85820072"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-none">	Ignored_server_ids: 3, 2, 6, 9</code></pre>
      </div>
     </div>
     <p>
      <code class="literal">
       Replicate_Ignore_Server_Ids
      </code>
      filtering is
            performed by the I/O (receiver) thread, rather than by the
            SQL (applier) thread, which means that events which are
            filtered out are not written to the relay log. This differs
            from the filtering actions taken by server options such
      <a class="link" href="replication-options-replica.html#option_mysqld_replicate-do-table">
       <code class="option">
        --replicate-do-table
       </code>
      </a>
      , which
            apply to the applier thread.
     </p>
     <p>
      If
      <code class="literal">
       SET gtid_mode=ON
      </code>
      is issued when any
            channel has existing server IDs set with
      <a class="link" href="change-replication-source-to.html#crs-opt-ignore_server_ids">
       <code class="literal">
        IGNORE_SERVER_IDS
       </code>
      </a>
      , the
            statement is rejected with an error. Before starting
            GTID-based replication, use
      <a class="link" href="show-replica-status.html" title="15.7.7.35 SHOW REPLICA STATUS Statement">
       <code class="literal">
        SHOW
            REPLICA STATUS
       </code>
      </a>
      to check for and clear all ignored
            server ID lists on the servers involved. You can clear a
            list by issuing a
      <a class="link" href="change-replication-source-to.html" title="15.4.2.2 CHANGE REPLICATION SOURCE TO Statement">
       <code class="literal">
        CHANGE REPLICATION
            SOURCE TO
       </code>
      </a>
      statement using
      <code class="literal">
       IGNORE_SERVER_IDS=()
      </code>
      —that is, with
            an empty list of server IDs.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Source_Server_Id
      </code>
     </p>
     <p>
      The
      <a class="link" href="replication-options.html#sysvar_server_id">
       <code class="literal">
        server_id
       </code>
      </a>
      value from
            the source.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Source_UUID
      </code>
     </p>
     <p>
      The
      <a class="link" href="replication-options.html#sysvar_server_uuid">
       <code class="literal">
        server_uuid
       </code>
      </a>
      value from
            the source.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Source_Info_File
      </code>
     </p>
     <p>
      The location of the
      <code class="filename">
       master.info
      </code>
      file,
            the use of which is now deprecated. By default, a table is
            used instead for the replica's connection metadata
            repository.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       SQL_Delay
      </code>
     </p>
     <p>
      The number of seconds that the replica must lag the source.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       SQL_Remaining_Delay
      </code>
     </p>
     <p>
      When
      <code class="literal">
       Replica_SQL_Running_State
      </code>
      is
      <code class="literal">
       Waiting until SOURCE_DELAY seconds after source
            executed event
      </code>
      , this field contains the number of
            delay seconds remaining. At other times, this field is
      <code class="literal">
       NULL
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Replica_SQL_Running_State
      </code>
     </p>
     <p>
      The state of the SQL thread (analogous to
      <code class="literal">
       Replica_IO_State
      </code>
      ). The value is identical
            to the
      <code class="literal">
       State
      </code>
      value of the SQL thread as
            displayed by
      <a class="link" href="show-processlist.html" title="15.7.7.31 SHOW PROCESSLIST Statement">
       <code class="literal">
        SHOW
            PROCESSLIST
       </code>
      </a>
      .
      <a class="xref" href="replica-sql-thread-states.html" title="10.14.6 Replication SQL Thread States">
       Section 10.14.6, “Replication SQL Thread States”
      </a>
      , provides a
            listing of possible states.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Source_Retry_Count
      </code>
     </p>
     <p>
      The number of times the replica can attempt to reconnect to
            the source in the event of a lost connection. This value can
            be set using the
      <code class="literal">
       SOURCE_RETRY_COUNT
      </code>
      option of the
      <a class="link" href="change-replication-source-to.html" title="15.4.2.2 CHANGE REPLICATION SOURCE TO Statement">
       <code class="literal">
        CHANGE REPLICATION SOURCE
            TO
       </code>
      </a>
      statement.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Source_Bind
      </code>
     </p>
     <p>
      The network interface that the replica is bound to, if any.
            This is set using the
      <code class="literal">
       SOURCE_BIND
      </code>
      option
            for the
      <a class="link" href="change-replication-source-to.html" title="15.4.2.2 CHANGE REPLICATION SOURCE TO Statement">
       <code class="literal">
        CHANGE REPLICATION SOURCE
            TO
       </code>
      </a>
      statement.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Last_IO_Error_Timestamp
      </code>
     </p>
     <p>
      A timestamp in
      <em class="replaceable">
       <code>
        YYMMDD hh:mm:ss
       </code>
      </em>
      format that shows when the most recent I/O error took place.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Last_SQL_Error_Timestamp
      </code>
     </p>
     <p>
      A timestamp in
      <em class="replaceable">
       <code>
        YYMMDD hh:mm:ss
       </code>
      </em>
      format that shows when the most recent SQL error occurred.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Retrieved_Gtid_Set
      </code>
     </p>
     <p>
      The set of global transaction IDs corresponding to all
            transactions received by this replica. Empty if GTIDs are
            not in use. See
      <a class="xref" href="replication-gtids-concepts.html#replication-gtids-concepts-gtid-sets" title="GTID Sets">
       GTID Sets
      </a>
      for
            more information.
     </p>
     <p>
      This is the set of all GTIDs that exist or have existed in
            the relay logs. Each GTID is added as soon as the
      <code class="literal">
       Gtid_log_event
      </code>
      is received. This can
            cause partially transmitted transactions to have their GTIDs
            included in the set.
     </p>
     <p>
      When all relay logs are lost due to executing
      <a class="link" href="reset-replica.html" title="15.4.2.3 RESET REPLICA Statement">
       <code class="literal">
        RESET REPLICA
       </code>
      </a>
      or
      <a class="link" href="change-replication-source-to.html" title="15.4.2.2 CHANGE REPLICATION SOURCE TO Statement">
       <code class="literal">
        CHANGE REPLICATION SOURCE TO
       </code>
      </a>
      ,
            or due to the effects of the
      <a class="link" href="replication-options-replica.html#sysvar_relay_log_recovery">
       <code class="option">
        --relay-log-recovery
       </code>
      </a>
      option,
            the set is cleared. When
      <a class="link" href="replication-options-replica.html#sysvar_relay_log_purge">
       <code class="literal">
        relay_log_purge = 1
       </code>
      </a>
      , the
            newest relay log is always kept, and the set is not cleared.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Executed_Gtid_Set
      </code>
     </p>
     <p>
      The set of global transaction IDs written in the binary log.
            This is the same as the value for the global
      <a class="link" href="replication-options-gtids.html#sysvar_gtid_executed">
       <code class="literal">
        gtid_executed
       </code>
      </a>
      system
            variable on this server, as well as the value for
      <code class="literal">
       Executed_Gtid_Set
      </code>
      in the output of
      <a class="link" href="show-binary-log-status.html" title="15.7.7.1 SHOW BINARY LOG STATUS Statement">
       <code class="literal">
        SHOW BINARY LOG STATUS
       </code>
      </a>
      on
            this server. Empty if GTIDs are not in use. See
      <a class="xref" href="replication-gtids-concepts.html#replication-gtids-concepts-gtid-sets" title="GTID Sets">
       GTID Sets
      </a>
      for
            more information.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Auto_Position
      </code>
     </p>
     <p>
      1 if GTID auto-positioning is in use for the channel,
            otherwise 0.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Replicate_Rewrite_DB
      </code>
     </p>
     <p>
      The
      <code class="literal">
       Replicate_Rewrite_DB
      </code>
      value displays
            any replication filtering rules that were specified. For
            example, if the following replication filter rule was set:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting one-line language-sql"><div class="docs-select-all right" id="sa91261178"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-sql"><span class="token keyword">CHANGE</span> <span class="token keyword">REPLICATION</span> <span class="token keyword">FILTER</span> <span class="token keyword">REPLICATE_REWRITE_DB</span><span class="token operator">=</span><span class="token punctuation">(</span><span class="token punctuation">(</span>db1<span class="token punctuation">,</span>db2<span class="token punctuation">)</span><span class="token punctuation">,</span> <span class="token punctuation">(</span>db3<span class="token punctuation">,</span>db4<span class="token punctuation">)</span><span class="token punctuation">)</span><span class="token punctuation">;</span></code></pre>
     </div>
     <p>
      the
      <code class="literal">
       Replicate_Rewrite_DB
      </code>
      value displays:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting one-line language-none"><div class="docs-select-all right" id="sa18977488"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-none">Replicate_Rewrite_DB: (db1,db2),(db3,db4)</code></pre>
     </div>
     <p>
      For more information, see
      <a class="xref" href="change-replication-filter.html" title="15.4.2.1 CHANGE REPLICATION FILTER Statement">
       Section 15.4.2.1, “CHANGE REPLICATION FILTER Statement”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Channel_name
      </code>
     </p>
     <p>
      The replication channel which is being displayed. There is
            always a default replication channel, and more replication
            channels can be added. See
      <a class="xref" href="replication-channels.html" title="19.2.2 Replication Channels">
       Section 19.2.2, “Replication Channels”
      </a>
      for more information.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Master_TLS_Version
      </code>
     </p>
     <p>
      The TLS version used on the source. For TLS version
            information, see
      <a class="xref" href="encrypted-connection-protocols-ciphers.html" title="8.3.2 Encrypted Connection TLS Protocols and Ciphers">
       Section 8.3.2, “Encrypted Connection TLS Protocols and Ciphers”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Source_public_key_path
      </code>
     </p>
     <p>
      The path name to a file containing a replica-side copy of
            the public key required by the source for RSA key pair-based
            password exchange. The file must be in PEM format. This
            column applies to replicas that authenticate with the
      <code class="literal">
       sha256_password
      </code>
      (deprecated) or
      <code class="literal">
       caching_sha2_password
      </code>
      authentication
            plugin.
     </p>
     <p>
      If
      <code class="literal">
       Source_public_key_path
      </code>
      is given and
            specifies a valid public key file, it takes precedence over
      <code class="literal">
       Get_source_public_key
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Get_source_public_key
      </code>
     </p>
     <p>
      Whether to request from the source the public key required
            for RSA key pair-based password exchange. This column
            applies to replicas that authenticate with the
      <code class="literal">
       caching_sha2_password
      </code>
      authentication
            plugin. For that plugin, the source does not send the public
            key unless requested.
     </p>
     <p>
      If
      <code class="literal">
       Source_public_key_path
      </code>
      is given and
            specifies a valid public key file, it takes precedence over
      <code class="literal">
       Get_source_public_key
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       Network_Namespace
      </code>
     </p>
     <p>
      The network namespace name; empty if the connection uses the
            default (global) namespace. For information about network
            namespaces, see
      <a class="xref" href="network-namespace-support.html" title="7.1.14 Network Namespace Support">
       Section 7.1.14, “Network Namespace Support”
      </a>
      .
     </p>
    </li>
   </ul>
  </div>
 </div>
 <br/>
</div>
