我想用canal实时同步mysql的数据到elasticsearch，但是canal总有这个，请问该怎么解决
2019-04-01 23:03:52.484 [Thread-7] INFO com.alibaba.otter.canal.deployer.CanalStater - ## stop the canal server
2019-04-01 23:03:52.484 [Thread-8] INFO com.alibaba.otter.canal.kafka.CanalKafkaProducer - ## stop the kafka producer
2019-04-01 23:03:52.490 [Thread-8] INFO com.alibaba.otter.canal.kafka.CanalKafkaProducer - ## kafka producer is down.
2019-04-01 23:03:52.928 [Thread-7] INFO com.alibaba.otter.canal.deployer.CanalController - ## stop the canal server[192.168.8.162:3406]
2019-04-01 23:03:52.935 [Thread-7] INFO com.alibaba.otter.canal.deployer.CanalStater - ## canal server is down.
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=96m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: UseCMSCompactAtFullCollection is deprecated and will likely be removed in a future release.
2019-04-01 23:04:00.191 [main] INFO com.alibaba.otter.canal.deployer.CanalLauncher - ## set default uncaught exception handler
2019-04-01 23:04:00.219 [main] INFO com.alibaba.otter.canal.deployer.CanalLauncher - ## load canal configurations
2019-04-01 23:04:00.222 [main] INFO c.a.o.c.d.monitor.remote.RemoteConfigLoaderFactory - ## load local canal configurations
2019-04-01 23:04:00.232 [main] INFO com.alibaba.otter.canal.deployer.CanalStater - ## start the canal server.
2019-04-01 23:04:00.351 [main] INFO com.alibaba.otter.canal.deployer.CanalController - ## start the canal server[192.168.8.162:3406]
2019-04-01 23:04:00.784 [main] WARN o.s.beans.GenericTypeAwarePropertyDescriptor - Invalid JavaBean property 'connectionCharset' being accessed! Ambiguous write methods found next to actually used [public void com.alibaba.otter.canal.parse.inbound.mysql.AbstractMysqlEventParser.setConnectionCharset(java.nio.charset.Charset)]: [public void com.alibaba.otter.canal.parse.inbound.mysql.AbstractMysqlEventParser.setConnectionCharset(java.lang.String)]
2019-04-01 23:04:00.800 [main] WARN c.a.o.canal.parse.inbound.mysql.dbsync.LogEventConvert - --> init table filter : ^.*..*$
2019-04-01 23:04:00.800 [main] WARN c.a.o.canal.parse.inbound.mysql.dbsync.LogEventConvert - --> init table black filter :
2019-04-01 23:04:00.842 [destination = example , address = /127.0.0.1:3306 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - ---> begin to find start position, it will be long time for reset or first position
2019-04-01 23:04:00.852 [destination = example , address = /127.0.0.1:3306 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - prepare to find start position just last position
{"identity":{"slaveId":-1,"sourceAddress":{"address":"localhost","port":3306}},"postion":{"gtid":"","included":false,"journalName":"mysql-bin.000001","position":3960,"serverId":1,"timestamp":1554116405000}}
2019-04-01 23:04:00.864 [destination = example , address = /127.0.0.1:3306 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - ---> find start position successfully, EntryPosition[included=false,journalName=mysql-bin.000001,position=3960,serverId=1,gtid=,timestamp=1554116405000] cost : 10ms , the next step is binlog dump
2019-04-01 23:04:00.868 [main] WARN c.a.o.canal.parse.inbound.mysql.dbsync.LogEventConvert - --> init table filter : ^.*..*$
2019-04-01 23:04:00.869 [main] WARN c.a.o.canal.parse.inbound.mysql.dbsync.LogEventConvert - --> init table black filter :
2019-04-01 23:04:00.871 [main] INFO com.alibaba.otter.canal.deployer.CanalStater - ## the canal server is running now ......
##2019-04-01 23:04:00.874 [destination = metrics , address = null , EventParser] ERROR c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - parse events has an error
##com.alibaba.otter.canal.parse.exception.CanalParseException: illegal connection is null
2019-04-01 23:04:00.880 [canal-instance-scan-0] INFO c.a.o.canal.deployer.monitor.SpringInstanceConfigMonitor - auto notify stop metrics successful.
