<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h3 class="title">
      <a name="source-thread-states">
      </a>
      10.14.4 Replication Source Thread States
     </h3>
    </div>
   </div>
  </div>
  <a class="indexterm" name="idm46045221307232">
  </a>
  <a class="indexterm" name="idm46045221305776">
  </a>
  <p>
   The following list shows the most common states you may see in
        the
   <code class="literal">
    State
   </code>
   column for the
   <code class="literal">
    Binlog
        Dump
   </code>
   thread of the replication source. If you see no
   <code class="literal">
    Binlog Dump
   </code>
   threads on a source, this means
        that replication is not running; that is, that no replicas are
        currently connected.
  </p>
  <p>
   In MySQL 8.0, incompatible changes were made to instrumentation
        names. Monitoring tools that work with these instrumentation
        names might be impacted. If the incompatible changes have an
        impact for you, set the
   <a class="link" href="replication-options-replica.html#sysvar_terminology_use_previous">
    <code class="literal">
     terminology_use_previous
    </code>
   </a>
   system
        variable to
   <code class="literal">
    BEFORE_8_0_26
   </code>
   to make MySQL
        Server use the old versions of the names for the objects
        specified in the previous list. This enables monitoring tools
        that rely on the old names to continue working until they can be
        updated to use the new names.
  </p>
  <p>
   Set the
   <a class="link" href="replication-options-replica.html#sysvar_terminology_use_previous">
    <code class="literal">
     terminology_use_previous
    </code>
   </a>
   system
        variable with session scope to support individual functions, or
        global scope to be a default for all new sessions. When global
        scope is used, the slow query log contains the old versions of
        the names.
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <a class="indexterm" name="idm46045221294192">
      </a>
      <a class="indexterm" name="idm46045221292672">
      </a>
      <code class="literal">
       Finished reading one binlog; switching to next
            binlog
      </code>
     </p>
     <p>
      The thread has finished reading a binary log file and is
            opening the next one to send to the replica.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a class="indexterm" name="idm46045221289104">
      </a>
      <a class="indexterm" name="idm46045221287568">
      </a>
      <code class="literal">
       Master has sent all binlog to slave; waiting for
            more updates
      </code>
     </p>
     <p>
      <a class="indexterm" name="idm46045221284896">
      </a>
      <a class="indexterm" name="idm46045221283360">
      </a>
      <code class="literal">
       Source has sent all binlog to replica; waiting for
            more updates
      </code>
     </p>
     <p>
      The thread has read all remaining updates from the binary
            logs and sent them to the replica. The thread is now idle,
            waiting for new events to appear in the binary log resulting
            from new updates occurring on the source.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a class="indexterm" name="idm46045221279632">
      </a>
      <a class="indexterm" name="idm46045221278128">
      </a>
      <code class="literal">
       Sending binlog event to slave
      </code>
     </p>
     <p>
      <a class="indexterm" name="idm46045221275536">
      </a>
      <a class="indexterm" name="idm46045221274032">
      </a>
      <code class="literal">
       Sending binlog event to replica
      </code>
     </p>
     <p>
      Binary logs consist of
      <span class="emphasis">
       <em>
        events
       </em>
      </span>
      , where an
            event is usually an update plus some other information. The
            thread has read an event from the binary log and is now
            sending it to the replica.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a class="indexterm" name="idm46045221269984">
      </a>
      <a class="indexterm" name="idm46045221268480">
      </a>
      <code class="literal">
       Waiting to finalize termination
      </code>
     </p>
     <p>
      A very brief state that occurs as the thread is stopping.
     </p>
    </li>
   </ul>
  </div>
 </div>
 <br/>
</div>
