Is it possible to restore replication?

Question

MySQL

There are 2 servers with master-master replication, but one of the servers had an error and replication did not work, as a result there was a big backlog, at the moment there is an error in the logs:

Version: '5.5.44-MariaDB-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
161106 22:42:32 [Note] Slave I/O thread: connected to master '[email protected]:3306',replication started in log 'mysql-bin.000068' at position 97123
161106 22:42:32 [ERROR] Error reading packet from server: Could not find first log file name in binary log index file ( server_errno=1236)
161106 22:42:32 [ERROR] Slave I/O: Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file', Error_code: 1236
161106 22:42:32 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000068', position 97123

The problem is that the mysql-bin.000068 file is no longer on the main server, there is only mysql-bin.000089, etc.
Status:

Slave_IO_State 	
Master_Host 	{IP}
Master_User 	replication_user
Master_Port 	3306
Connect_Retry 	60
Master_Log_File 	mysql-bin.000068
Read_Master_Log_Pos 	97123
Relay_Log_File 	mysql-relay-bin.000002
Relay_Log_Pos 	4
Relay_Master_Log_File 	mysql-bin.000068
Slave_IO_Running 	No
Slave_SQL_Running 	Yes
Replicate_Do_DB 	
Replicate_Ignore_DB 	information_schema, performance_schema
Replicate_Do_Table 	
Replicate_Ignore_Table 	queue
Replicate_Wild_Do_Table 	
Replicate_Wild_Ignore_Table 	queue
Last_Errno 	0
Last_Error 	
Skip_Counter 	0
Exec_Master_Log_Pos 	97123
Relay_Log_Space 	245
Until_Condition 	None
Until_Log_File 	
Until_Log_Pos 	0
Master_SSL_Allowed 	No
Master_SSL_CA_File 	
Master_SSL_CA_Path 	
Master_SSL_Cert 	
Master_SSL_Cipher 	
Master_SSL_Key 	
Seconds_Behind_Master

Do I understand correctly that it is no longer possible to continue normal replication and it will be necessary to dump all the databases on the main server, deploy it on the second one and reconfigure replication?

Answer 1

yes, you understand everything correctly.
select the "good" server, reload the "bad" one from it, restart replication.
howto