anchor.diff:  2017-03-27 17:03:46,742 - INFO  [main-EventThread:ZkClient@713] - zookeeper state changed (SyncConnected)
   2017-03-27 17:03:46,915 - INFO  [main:Logging$class@70] - Cluster ID = pE8NMeZqTaqmolK4WSVVlA
   2017-03-27 17:03:46,921 - WARN  [main:Logging$class@85] - No meta.properties file under dir /kafka/data/1/meta.properties
  -2017-03-27 17:03:46,941 - INFO  [ThrottledRequestReaper-Produce:Logging$class@70] - [ThrottledRequestReaper-Produce], Starting 
  -2017-03-27 17:03:46,941 - INFO  [ThrottledRequestReaper-Fetch:Logging$class@70] - [ThrottledRequestReaper-Fetch], Starting 
  +2017-03-27 17:03:46,941 - INFO  [ThrottledRequestReaper-Produce:Logging$class@70] - [ThrottledRequestReaper-Produce], Starting
  +2017-03-27 17:03:46,941 - INFO  [ThrottledRequestReaper-Fetch:Logging$class@70] - [ThrottledRequestReaper-Fetch], Starting
   2017-03-27 17:03:46,969 - INFO  [main:Logging$class@70] - Loading logs.
   2017-03-27 17:03:46,976 - INFO  [main:Logging$class@70] - Logs loading complete in 6 ms.
   2017-03-27 17:03:47,041 - INFO  [main:Logging$class@70] - Starting log cleanup with a period of 300000 ms.
   2017-03-27 17:03:47,043 - INFO  [main:Logging$class@70] - Starting log flusher with a default period of 9223372036854775807 ms.
   2017-03-27 17:03:47,078 - INFO  [main:Logging$class@70] - Awaiting socket connections on 172.17.0.3:9092.
   2017-03-27 17:03:47,081 - INFO  [main:Logging$class@70] - [Socket Server on Broker 1], Started 1 acceptor threads
  -2017-03-27 17:03:47,098 - INFO  [ExpirationReaper-1:Logging$class@70] - [ExpirationReaper-1], Starting 
  -2017-03-27 17:03:47,101 - INFO  [ExpirationReaper-1:Logging$class@70] - [ExpirationReaper-1], Starting 
  +2017-03-27 17:03:47,098 - INFO  [ExpirationReaper-1:Logging$class@70] - [ExpirationReaper-1], Starting
  +2017-03-27 17:03:47,101 - INFO  [ExpirationReaper-1:Logging$class@70] - [ExpirationReaper-1], Starting
   2017-03-27 17:03:47,127 - INFO  [main:Logging$class@70] - Creating /controller (is it secure? false)
   2017-03-27 17:03:47,137 - INFO  [main:Logging$class@70] - Result of znode creation is: OK
   2017-03-27 17:03:47,138 - INFO  [main:Logging$class@70] - 1 successfully elected as leader
  -2017-03-27 17:03:47,215 - INFO  [ExpirationReaper-1:Logging$class@70] - [ExpirationReaper-1], Starting 
  -2017-03-27 17:03:47,219 - INFO  [ExpirationReaper-1:Logging$class@70] - [ExpirationReaper-1], Starting 
  -2017-03-27 17:03:47,220 - INFO  [ExpirationReaper-1:Logging$class@70] - [ExpirationReaper-1], Starting 
  +2017-03-27 17:03:47,215 - INFO  [ExpirationReaper-1:Logging$class@70] - [ExpirationReaper-1], Starting
  +2017-03-27 17:03:47,219 - INFO  [ExpirationReaper-1:Logging$class@70] - [ExpirationReaper-1], Starting
  +2017-03-27 17:03:47,220 - INFO  [ExpirationReaper-1:Logging$class@70] - [ExpirationReaper-1], Starting
   2017-03-27 17:03:47,229 - INFO  [main:Logging$class@70] - [GroupCoordinator 1]: Starting up.
   2017-03-27 17:03:47,230 - INFO  [main:Logging$class@70] - [GroupCoordinator 1]: Startup complete.
   2017-03-27 17:03:47,231 - INFO  [group-metadata-manager-0:Logging$class@70] - [Group Metadata Manager on Broker 1]: Removed 0 expired offsets in 1 milliseconds.
  
positive.code: }
  ----
  
  Here, we can see that the connector is running a single task (e.g., task 0) to do its work. The MySQL connector only supports a single task, since MySQL records all of its activities in one sequential binlog and so the MySQL connector needs only one reader to get a consistent and totally ordered view of all of those events. 
  
  If we look at the output of our `connect` container, we see that the connector has generated a lot of output. The first few lines related to our connector are output by Kafka Connect, and start with:
  
  
negative.code:     4 rows in set (0.00 sec)
  ----
  
  As we can see, all of our event records match the database.
  
  Now that we're monitoring changes, what happens when we *change* one of the records in the database? Run the following statement in the MySQL command line client:
  
  