05 - 2 Configure mysql replication using binlog and positionn part 2

Check my course on mysql replication

What is MySQL Replication?
replication enables data from one MySQL server (the master) to be replicated to one or more MySQL servers (the slaves). MySQL Replication is very easy to set up and is used to scale out read workloads, provide high availability and geographic redundancy, and offload backups and analytic jobs
Replication Scheme:
• Asynchronous replication
• Semi-synchronous replication
Global Transaction Identifier (GTID)
Replication in MySQL 5.5 and Earlier
How GTID Solves the Problem
Multi-Threaded Slave
Crash-Safe Slave
Group Commit

Please Follow me on Social Media

[Iginhn]

May I know if what application did you use for executing that commands? I am a newbie here, thanks.

[korshak]

great video, put a like. But it seems an old legacy method of replication. I found in mysql doc: "MySQL 8.0 supports different methods of replication. The traditional method is based on replicating events from the source's binary log, and requires the log files and positions in them to be synchronized between source and replica. The newer method based on global transaction identifiers (GTIDs) is transactional and therefore does not require working with log files or positions within these files, which greatly simplifies many common replication tasks." Could you make a video about "newer method based on global transaction " ?

[salman]

I am not finding Chage master to master info in dump, can you please suggest?

[fahdbahoo]

Mughees bhai, can a slave be the master of another slave ? and can a master have many slaves ?

[usas]

Last_SQL_Error: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 1 failed executing transaction 'ANONYMOUS' at master log binlog.000010, end_log_pos 366. See error log and/or table for more details about this failure or others, if any.