Shulou(Shulou.com)06/01 Report--

Recently, the computer room has been poisoned, and the network is often abnormal, which often leads to the interruption of MySQL replication. The previous errors were reported to Got fatal error 1236: 'error reading log entry' from master when reading data from binary log, but today there is a strange phenomenon. Everything is normal on the show slave status from the database, but there is no connection to the main database, and no abnormality is found in the library log. Therefore, the task of regularly checking slave status in my crontab can no longer detect errors, and there is no way for stop slave;start slave; replication to return to normal. [@ more@]

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.