replication - why issue 'reset master' when resyncing a mysql slave -

Ive recently performed a few DB resync and have a question (what appears to be) a 'reset master' Before dubbing the db.

Just before dumping the database from master to all the documents around this process, there is a 'Reset Master'.

Example:

In a production environment, however, it seems mainly per-productive because the 'Reset Master' command will clear existing binary logs. So if something goes wrong with your master, when the replica breaks down, you end up with an inconsistent / corrupt master and outside the sync slave

this Given that this process should be done in the first place (i.e., something has gone wrong with mysql replication), it seems foolish to wipe out the binologies (which can be used to recover the entire disaster) just because Central Slave requires re throne.

What exactly am I asking: What am I missing - is there any legitimate reason for a 'reset master' before taking a dump from the master?

It is not necessary if you use mysqldump to create a dump, then add this option : - Single-transaction - In order to lock the Inodb tables and create continuous snapshots, add the binary log position of the master, - master-data - copy the pulse Should start.