MySQL 8 replication?

Question

MySQL

Hello, I

ran into this problem, after reading the manuals, a couple of questions arose on MySQL replication

There is a "max_binlog_size" parameter in the configuration file
Do I understand correctly that in the event of a slave failure, for some conditional amount of time for which mysql-bin.log will run when the conditional 100M is reached, then when the slave server is restored, the data that is already in the archive log will not be written? How then to correctly calculate the size of the log file?

Is it possible to load a hot base dump into the master during master-slave operation? i.e. mysql database < database.sql

If the slave is not set to read-only, what will happen when data changed on the slave is affected during replication?

Answer 1

Do I understand correctly that if the slave fails for some conditional amount of time during which mysql-bin.log will run when the conditional 100M is reached, then when the slave server is restored, the data that is already in the archive log will not be written?

No, it's wrong.
max_binlog_size sets the size of ONE log file. When the specified size is reached, a new one is created, and the record goes to it. And the old one does not go anywhere, and will be normally transferred to the slave when its functioning is restored.