5 Incorporated comments
source | link

@DTest gave you theThe Primary thing you need to do. was left in a comment:

Follow the suggestion in Duplicate entry in MySQL slave:

STOP SLAVE;
SET GLOBAL sql_slave_skip_counter=1;
START SLAVE;

However, here is how you can start off at the better position with the CHANGE MASTER TOCHANGE MASTER TO command.

So, the CHANGE MASTER TOCHANGE MASTER TO in this case would be:

This will erase any relay logs collected and start collecting with a fresh, empty relay log.

UPDATE 2011-01-04 13:25 EDT

We stopped at log 'mysql1-bin.000362' position 3384732.

Good news !!! You just posted this : We stopped at log 'mysql1-bin.000362' position 3384732. That's what you use.:

UPDATE 2011-01-04 13:52 EDT

If you ran RESET SLAVERESET SLAVE on the Slave, do not despair. Just run the full syntax version of the CHANGE MASTER TO command:

@DTest gave you the Primary thing you need to do.

However, here is how you can start off at the better position with the CHANGE MASTER TO command.

So, the CHANGE MASTER TO in this case would be:

This will erase any relay logs collected and start collecting with a fresh, empty relay log

UPDATE 2011-01-04 13:25 EDT

Good news !!! You just posted this : We stopped at log 'mysql1-bin.000362' position 3384732. That's what you use.

UPDATE 2011-01-04 13:52 EDT

If you ran RESET SLAVE on the Slave, do not despair. Just run the full syntax version of the CHANGE MASTER TO command:

The Primary thing you need to do was left in a comment:

Follow the suggestion in Duplicate entry in MySQL slave:

STOP SLAVE;
SET GLOBAL sql_slave_skip_counter=1;
START SLAVE;

However, here is how you can start off at the better position with the CHANGE MASTER TO command.

So, the CHANGE MASTER TO in this case would be:

This will erase any relay logs collected and start collecting with a fresh, empty relay log.

We stopped at log 'mysql1-bin.000362' position 3384732.

That's what you use:

If you ran RESET SLAVE on the Slave, do not despair. Just run the full syntax version of the CHANGE MASTER TO command:

4 replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
source | link

Step 07) If replication breaks due to Error 1062 (Duplicate Key), now you can implement @DTest's suggestionimplement @DTest's suggestion. Then, goto Step 06. Repeat this until Seconds_Behind_Master go to 0.

Step 07) If replication breaks due to Error 1062 (Duplicate Key), now you can implement @DTest's suggestion. Then, goto Step 06. Repeat this until Seconds_Behind_Master go to 0.

Step 07) If replication breaks due to Error 1062 (Duplicate Key), now you can implement @DTest's suggestion. Then, goto Step 06. Repeat this until Seconds_Behind_Master go to 0.

3 added 410 characters in body
source | link

UPDATE 2011-01-04 13:52 EDT

If you ran RESET SLAVE on the Slave, do not despair. Just run the full syntax version of the CHANGE MASTER TO command:

CHANGE MASTER TO
MASTER_HOST='IP Address of Master',
MASTER_PORT=3306,
MASTER_USER='Replication Username',
MASTER_PASSWORD='Replication Password',
MASTER_LOG_FILE='mysql1-bin.000362',
MASTER_LOG_POS=3384732;

UPDATE 2011-01-04 13:52 EDT

If you ran RESET SLAVE on the Slave, do not despair. Just run the full syntax version of the CHANGE MASTER TO command:

CHANGE MASTER TO
MASTER_HOST='IP Address of Master',
MASTER_PORT=3306,
MASTER_USER='Replication Username',
MASTER_PASSWORD='Replication Password',
MASTER_LOG_FILE='mysql1-bin.000362',
MASTER_LOG_POS=3384732;
2 added 20 characters in body
source | link
1
source | link