business_doc/maxwell常见错误处理.md

@@ -57,4 +57,26 @@ kafka.buffer.memory=5242880这两个参数，使数据尽量不落地磁盘
 处理方法：多次重启至选择目标server_id（不建议）；
 或者将库中除目标server_id对应的schema外的多份schema和库表全部清除，然后重启至选择目标server_id（可行，不推荐）；
 或者将对应mysql实例在maxwell元数据库中所有的schema清除，但是记得记录down掉时的binlog的position，然后启动maxwell，后停止修改binlog的position的之前记录的位置，再启动maxwell，如果有已存在的表或者不存在的表再手动补充即可
+```
+
+## java.util.concurrent.TimeoutException: BinaryLogClient was unable to connect in 5000ms
+
+```
+错误日志内容:
+900578196 [INFO] BinlogConnectorReplicator: Binlog disconnected.
+900578224 [WARN] BinlogConnectorReplicator: replicator stopped at position: mysql-bin.017926:327525750 -- restarting
+900583225 [WARN] BinaryLogClient: Failed to establish connection in 4999ms. Forcing disconnect.
+900583230 [INFO] TaskManager: Stopping 5 tasks
+900583230 [ERROR] TaskManager: cause:
+java.util.concurrent.TimeoutException: BinaryLogClient was unable to connect in 5000ms
+        at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:877) ~[mysql-binlog-connector-java-0.24.0.jar:0.24.0]
+        at com.zendesk.maxwell.replication.BinlogConnectorReplicator.ensureReplicatorThread(BinlogConnectorReplicator.java:448) ~[maxwell-1.30.0.jar:1.30.0]
+        at com.zendesk.maxwell.replication.BinlogConnectorReplicator.getRow(BinlogConnectorReplicator.java:617) ~[maxwell-1.30.0.jar:1.30.0]
+        at com.zendesk.maxwell.replication.BinlogConnectorReplicator.work(BinlogConnectorReplicator.java:180) ~[maxwell-1.30.0.jar:1.30.0]
+        at com.zendesk.maxwell.util.RunLoopProcess.runLoop(RunLoopProcess.java:34) ~[maxwell-1.30.0.jar:1.30.0]
+        at com.zendesk.maxwell.Maxwell.startInner(Maxwell.java:255) ~[maxwell-1.30.0.jar:1.30.0]
+        at com.zendesk.maxwell.Maxwell.start(Maxwell.java:183) ~[maxwell-1.30.0.jar:1.30.0]
+        at com.zendesk.maxwell.Maxwell.main(Maxwell.java:286) ~[maxwell-1.30.0.jar:1.30.0]
+错误原因:未知
+解决方案:重启对应的maxwell实例
 ```
\ No newline at end of file