ntpdate會導致mysql slow query log出現很大的query time
mysql官方有對此事的論述：
在我得系統裡我發現了這種事情：
mysql的日誌：
# Time: 080308 18:07:01
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 1 Rows_examined: 0
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 1 Rows_examined: 0
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 1 Rows_examined: 0
系統的ntpdate的日誌：
8 Mar 18:00:02 ntpdate[14503]: adjust time server 172.23.16.24 offset 0.009211 sec
TIMESERVER=172.23.16.24
HEADMARK 172.16.216.32 [2008-03-08 18:07][log]ntpdate query offset: 2
HEADMARK 172.16.216.32 [2008-03-08 18:07][log]ntpdate query offset: 2
HEADMARK 172.16.216.32 [2008-03-08 18:07][log]offset is 2, will run ntpdate now...
HEADMARK 172.16.216.32 [2008-03-08 18:07][log]offset is 2, will run ntpdate now...
Looking for host 172.23.16.24 and service ntp
8 Mar 18:07:01 ntpdate[14913]: step time server 172.23.16.24 offset -2.547730 sec
TIMESERVER=172.23.16.24
HEADMARK 172.16.216.32 [2008-03-08 18:14][log]ntpdate query offset: 0
HEADMARK 172.16.216.32 [2008-03-08 18:14][log]ntpdate query offset: 0
HEADMARK 172.16.216.32 [2008-03-08 18:14][log]offset is 0, will run ntpdate now...
HEADMARK 172.16.216.32 [2008-03-08 18:14][log]offset is 0, will run ntpdate now...
Looking for host 172.23.16.24 and service ntp
8 Mar 18:14:02 ntpdate[15184]: adjust time server 172.23.16.24 offset 0.014846 sec
TIMESERVER=172.23.16.24
HEADMARK 172.16.216.32 [2008-03-08 18:21][log]ntpdate query offset: 0
HEADMARK 172.16.216.32 [2008-03-08 18:21][log]ntpdate query offset: 0
HEADMARK 172.16.216.32 [2008-03-08 18:21][log]offset is 0, will run ntpdate now...
HEADMARK 172.16.216.32 [2008-03-08 18:21][log]offset is 0, will run ntpdate now...
Looking for host 172.23.16.24 and service ntp
8 Mar 18:21:01 ntpdate[15516]: adjust time server 172.23.16.24 offset 0.010321 sec
在我得系統裡我發現了這種事情：
mysql的日誌：
# Time: 080308 18:07:01
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 1 Rows_examined: 0
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 1 Rows_examined: 0
# Query_time: 4294967294 Lock_time: 0 Rows_sent: 1 Rows_examined: 0
系統的ntpdate的日誌：
8 Mar 18:00:02 ntpdate[14503]: adjust time server 172.23.16.24 offset 0.009211 sec
TIMESERVER=172.23.16.24
HEADMARK 172.16.216.32 [2008-03-08 18:07][log]ntpdate query offset: 2
HEADMARK 172.16.216.32 [2008-03-08 18:07][log]ntpdate query offset: 2
HEADMARK 172.16.216.32 [2008-03-08 18:07][log]offset is 2, will run ntpdate now...
HEADMARK 172.16.216.32 [2008-03-08 18:07][log]offset is 2, will run ntpdate now...
Looking for host 172.23.16.24 and service ntp
8 Mar 18:07:01 ntpdate[14913]: step time server 172.23.16.24 offset -2.547730 sec
TIMESERVER=172.23.16.24
HEADMARK 172.16.216.32 [2008-03-08 18:14][log]ntpdate query offset: 0
HEADMARK 172.16.216.32 [2008-03-08 18:14][log]ntpdate query offset: 0
HEADMARK 172.16.216.32 [2008-03-08 18:14][log]offset is 0, will run ntpdate now...
HEADMARK 172.16.216.32 [2008-03-08 18:14][log]offset is 0, will run ntpdate now...
Looking for host 172.23.16.24 and service ntp
8 Mar 18:14:02 ntpdate[15184]: adjust time server 172.23.16.24 offset 0.014846 sec
TIMESERVER=172.23.16.24
HEADMARK 172.16.216.32 [2008-03-08 18:21][log]ntpdate query offset: 0
HEADMARK 172.16.216.32 [2008-03-08 18:21][log]ntpdate query offset: 0
HEADMARK 172.16.216.32 [2008-03-08 18:21][log]offset is 0, will run ntpdate now...
HEADMARK 172.16.216.32 [2008-03-08 18:21][log]offset is 0, will run ntpdate now...
Looking for host 172.23.16.24 and service ntp
8 Mar 18:21:01 ntpdate[15516]: adjust time server 172.23.16.24 offset 0.010321 sec
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/82392/viewspace-201891/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- mysql 配置 General Query Log和# Slow Query LogMySql
- Mysql資料庫Slow_log中的lock_Time和Query_timeMySql資料庫
- MySQL Slow Query log(慢查詢日誌)MySql
- coca SLOW QUERY
- Mysql general query logMySql
- MySQL slow query [慢查詢] 資料整理MySql
- MySQL8.0：The General Query LogMySql
- 利用tcpdump簡易抓取MySQL Query LogTCPMySql
- Query the duration of log switch
- MySQL Query CacheMySql
- MySQL資料庫出現 Ignoring query to other databaseMySql資料庫Database
- 詳解MySQL慢日誌（上）query_time\start_time\lock_time 的坑MySql
- MySQL Rewriter Query Rewrite PluginMySqlPlugin
- 關於mysql的query_cacheMySql
- 【MySQL】慢日誌大量生成 long-query-time “失效”問題MySql
- 官答丨slow_query_log_file例項記憶體中變數與配置檔案設定的不一致記憶體變數
- DB2的Temporal表和Time Travel QueryDB2
- jdbc autoReconnect=true 引數設定導致 slow log 爆表。JDBC
- 解析MYSQL BINLOG 二進位制格式(3)--QUERY_EVENTMySql
- 11g 新特性 real time apply ＋real time queryAPP
- phpmysqlimysqli_query()mysqli_real_query()PHPMySql
- 查詢real-time apply、real-time query的檢視APP
- ELK收集mysql_slow.logMySql
- MySQL：慢SQL（slow_log）MySql
- proxysql mysql_query_rules 翻譯MySql
- MySQL ：Ignoring query to other databaseMySqlDatabase
- 【DG】Real-time query實時查詢操作
- 如何限制使用者修改long_query_time
- [MySQL Slow log]正確安全清空線上慢查詢日誌slow log的流程MySql
- Query sqlSQL
- Query DSL
- reg query /?
- MySQL slow log相關引數MySql
- 【Mysql】公開課之-Query-rewriteMySql
- Mysql 查詢快取 query_cacheMySql快取
- Mysql 會導致索引失效的情況MySql索引
- expdp 使用QUERY 匯出部分資料。
- 利用QUERY選項輸出資料