Fixing replication in GTID enabled MySQL

For years i have been using MySQL replication feature and faced so many replication issue and resolved them i.e. replication break due to master failure, server restart due to hardware problems, accidental data change on slave or primary key constraints issue. All such issues resolved by playing with mysql dump, binary files and positions.

Now MySQL introduced one of the best feature GTID based replication which is quite different from previous versions. And is is obvious that handling replication issue in GTID based replication needs different approach.