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 Slow Query log(慢查詢日誌)MySql
- coca SLOW QUERY
- MySQL8.0：The General Query LogMySql
- MySQL資料庫出現 Ignoring query to other databaseMySql資料庫Database
- binlog_rows_query_log_events
- MySQL的general_log和slow_logMySql
- 官答丨slow_query_log_file例項記憶體中變數與配置檔案設定的不一致記憶體變數
- ELK收集mysql_slow.logMySql
- MySQL：慢SQL（slow_log）MySql
- MySQL Rewriter Query Rewrite PluginMySqlPlugin
- 關於mysql的query_cacheMySql
- 如何限制使用者修改long_query_time
- LCA Online Query with O(N) Memory and O(1) Time Complexity
- reg query /?
- Query DSL
- mysql之 slow log 慢查詢日誌MySql
- ES 筆記十：Query String & Simple Query String筆記
- Flashback Query(轉)
- expdp query用法
- Elasticsearch——query stringElasticsearch
- PDO 的 exec 和 query
- drools中query的使用
- 級聯slave的延遲計算和query event exe time獲取方法
- Mysql 會導致索引失效的情況MySql索引
- react-query手把手教程①-入門react-queryReact
- Mysql mysql lost connection to server during query 問題解決方法MySqlServer
- DZ論壇MySQL Query Error Errno:1046錯誤MySqlError
- pt-query-digest
- [Typescript] Query builder exampleTypeScriptUI
- jpa @Query demo 演示
- Laravel query when 的查詢Laravel
- elasticsearch 的 update by query 使用案例Elasticsearch
- mysql的新建索引會導致insert被lockedMySql索引
- 除了GET方法，新的HTTP QUERY方法規範釋出HTTP
- mysqldump: Error 2013: Lost connection to MySQL server during query when dumpingMySqlErrorServer
- JDBC/MYSQL問題 : Unknown system variable 'query_cache_size'JDBCMySql
- Elasticsearch bool query小結Elasticsearch
- Rewrite %{QUERY_STRING}用法