A few questions about MySQL replication?

Question

MySQL

Not a bad article: https://habrahabr.ru/post/56702/
1. Could you give me more good articles on this topic
2. How much space do you need on the master for binary logs?... I have 10 gigabytes of free left
3. Binary logs are rotated by themselves, should their rotation be configured somewhere?
4. There is replication when the master "notifies the replica of changes" so 1 master can work with a maximum of 12 replicas, and there also seems to be a mode when the replica itself pulls changes from the master while it does nothing. Is there somewhere detailed information on these two modes, how to configure them, which one is better to use?

Answer 1

1 alas, I won’t tell you
2 it depends on the intensity of work with the database, if there are a lot of inserts, updates and deletions, then there will be a lot of logs
3 you need to configure max_binlog_size and expire_logs_days in my.cnf
4 umm ....
a) normally the master notifies the slave that something changed and the slave starts reading the master's binlog until it ends, and so on in a circle
b) I hear about 12 replicas for the first time, right now the production: mysql Server version: 5.5.46-log MySQL Community Server (GPL)
20+ slaves from it do replication
c) you are probably talking about semi-synchronous and asynchronous replication, by default replication is asynchronous and the slave can lag behind the master for various reasons (there was no connection or the slave could not keep up due to the performance of the master, etc.) but this does not affect the master in any way.
but you can configure it so that the master must wait for confirmation that the slave has also made changes, but this mode has many features, so if you don’t know why you need it, then you definitely don’t need it, and it’s often easier to use a galley cluster then.