WARN c.a.otter.canal.parse.inbound.mysql.MysqlEventParser - prepare to find start position just last position
{"identity":{"slaveId":-1,"sourceAddress":{"address":"xxxxx","port":xxxxxx}},"postion":{"included":false,"journalName":"mysql-bin.000004","position":75784970,"serverId":212,"timestamp":1513663476000}}
2017-12-19 14:08:33.488 [destination = CANAL , address = /xxxxx:xxxxxx, EventParser] ERROR c.a.otter.canal.parse.inbound.mysql.MysqlEventParser - dump address xxxxx:xxxxxx, has an error, retrying. caused by
java.nio.channels.ClosedByInterruptException: null
at com.alibaba.otter.canal.parse.driver.mysql.socket.SocketChannel.read(SocketChannel.java:49) ~[canal.parse.driver-1.0.25.jar:na]
at com.alibaba.otter.canal.parse.inbound.mysql.dbsync.DirectLogFetcher.fetch0(DirectLogFetcher.java:151) ~[canal.parse-1.0.25.jar:na]
at com.alibaba.otter.canal.parse.inbound.mysql.dbsync.DirectLogFetcher.fetch(DirectLogFetcher.java:69) ~[canal.parse-1.0.25.jar:na]
at com.alibaba.otter.canal.parse.inbound.mysql.MysqlConnection.dump(MysqlConnection.java:137) ~[canal.parse-1.0.25.jar:na]
at com.alibaba.otter.canal.parse.inbound.AbstractEventParser$3.run(AbstractEventParser.java:220) ~[canal.parse-1.0.25.jar:na]

otter部署为双向同步，一个节点正常，不报错， 另一个不支持ddl的node节点每隔2分钟报一次上面的错误，看了下binlog的位点，是到了最后的位点，binlog有没有新的日志写进来。 但是为什么另一个节点不报这个错误。 而且过了一段时间， channel 就挂点了，通过 manager启动channel 失败！！！！
查看manager的日志，报如下错误：

at java.util.concurrent.FutureTask.report(FutureTask.java:122) [na:1.8.0_131]
at java.util.concurrent.FutureTask.get(FutureTask.java:192) [na:1.8.0_131]
at com.alibaba.otter.shared.communication.core.impl.DefaultCommunicationClientImpl.call(DefaultCommunicationClientImpl.java:152) ~[shared.communication-4.2.16-SNAPSHOT.jar:na]
at com.alibaba.otter.manager.biz.remote.impl.ConfigRemoteServiceImpl.notifyChannel(ConfigRemoteServiceImpl.java:119) ~[manager.biz-4.2.16-SNAPSHOT.jar:na]
at com.alibaba.otter.manager.biz.remote.impl.ConfigRemoteServiceImpl$$FastClassByCGLIB$$3f77feba.invoke(<generated>) [cglib-nodep-2.2.jar:na]
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191) [cglib-nodep-2.2.jar:na]
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) [spring-aop-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) [spring-aop-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.springframework.aop.framework.adapter.ThrowsAdviceInterceptor.invoke(ThrowsAdviceInterceptor.java:124) [spring-aop-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) [spring-aop-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622) [spring-aop-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at com.alibaba.otter.manager.biz.remote.impl.ConfigRemoteServiceImpl$$EnhancerByCGLIB$$d8e5099b.notifyChannel(<generated>) [cglib-nodep-2.2.jar:na]
at com.alibaba.otter.manager.biz.config.channel.impl.ChannelServiceImpl$3.doInTransactionWithoutResult(ChannelServiceImpl.java:439) [manager.biz-4.2.16-SNAPSHOT.jar:na]
at org.springframework.transaction.support.TransactionCallbackWithoutResult.doInTransaction(TransactionCallbackWithoutResult.java:33) [spring-tx-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:130) [spring-tx-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at com.alibaba.otter.manager.biz.config.channel.impl.ChannelServiceImpl.switchChannelStatus(ChannelServiceImpl.java:378) [manager.biz-4.2.16-SNAPSHOT.jar:na]
at com.alibaba.otter.manager.biz.config.channel.impl.ChannelServiceImpl.startChannel(ChannelServiceImpl.java:462) [manager.biz-4.2.16-SNAPSHOT.jar:na]
at com.alibaba.otter.manager.biz.monitor.impl.RestartAlarmRecovery.processRecovery(RestartAlarmRecovery.java:103) [manager.biz-4.2.16-SNAPSHOT.jar:na]
at com.alibaba.otter.manager.biz.monitor.impl.RestartAlarmRecovery.access$100(RestartAlarmRecovery.java:44) [manager.biz-4.2.16-SNAPSHOT.jar:na]
at com.alibaba.otter.manager.biz.monitor.impl.RestartAlarmRecovery$1.run(RestartAlarmRecovery.java:137) [manager.biz-4.2.16-SNAPSHOT.jar:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_131]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_131]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_131]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131]

Caused by: com.alibaba.otter.shared.communication.core.exception.CommunicationException: call[10.11.4.185:20880] , Event[NotifyChannelEvent[channel=Channel[id=1,name=CHANNEL,status=START,description=,pipelines=[Pipeline[id=3,channelId=1,name=PIPLINE,description=,selectNodes=[Node[id=2,name=NODE,ip=10.11.4.185,port=30880,status=START,description=,parameters=NodeParameter[mbeanPort=30882,downloadPort=30881,zkCluster=AutoKeeperCluster[id=2,clusterName=zookeeper,serverList=[10.11.4.185:2181],description=,gmtCreate=2017-11-21 15:34:09,gmtModified=2017-11-21 。。。。。。。