Question
--------------mybinlog 日志穿越了,导致canal监控的es也穿越了,但是otter计算延迟的话,就乌龙了--------------
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER /*!*/;
# at 479763265
# 201109 21:54:47 server id 100 end_log_pos 479763335 Query thread_id=32101 exec_time=1 error_code=0
SET TIMESTAMP=1604930087/*!*/;
SET @@session.pseudo_thread_id=32101/*!*/;
SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=0, @@session.unique_checks=1, @@session.autocommit=1/*!*/;
SET @@session.sql_mode=1344274432/*!*/;
SET @@session.auto_increment_increment=1, @@session.auto_increment_offset=1/*!*/;
/*!\C utf8 *//*!*/;
SET @@session.character_set_client=33,@@session.collation_connection=33,@@session.collation_server=33/*!*/;
SET @@session.lc_time_names=0/*!*/;
SET @@session.collation_database=DEFAULT/*!*/;
COMMIT
/*!*/;
# at 479763335
# 201109 17:55:48 server id 100 end_log_pos 479763450 Query thread_id=31333 exec_time=14410 error_code=0
use tdxdb/*!*/;
SET TIMESTAMP=1604915748/*!*/;
SET @@session.pseudo_thread_id=31333/*!*/;
DROP /*!40005 TEMPORARY */ TABLE IF EXISTS `t2`,`t`
/*!*/;
DELIMITER ;
# End of log file
ROLLBACK /* added by mysqlbinlog */;
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
看日志,发现两条时间线:#201109 21:54:47 server id 100 end_log_pos 479763335
#201109 17:55:48 server id 100 end_log_pos 479763450
log日志的offset大的,为何时间戳反而小了?
咋办呢?
1条答案
按热度按时间yruzcnhs1#
昨天Kafka消费的时候发现消费信息里也有超过当天的未来时间戳出现.....