maria-discuss team mailing list archive
-
maria-discuss team
-
Mailing list archive
-
Message #05162
Replication Problem
-
To:
maria-discuss@xxxxxxxxxxxxxxxxxxx
-
From:
Thomas Plant <thomas@plant.systems>
-
Date:
Wed, 4 Jul 2018 12:03:26 +0200
-
Arc-authentication-results:
i=1; ORIGINATING; auth=pass smtp.auth=thomas@plant.systems smtp.mailfrom=thomas@plant.systems
-
Arc-message-signature:
i=1; a=rsa-sha256; c=relaxed/relaxed; d=plant.systems; s=arc; t=1530698609; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:in-reply-to: references; bh=xXU19JenVCZ+5qCyzIVOnnJKkbjtf2dxHGEFAeyF3TE=; b=KFgK+ULwsYAHXlzpvR7+Uf+QzWsEExbhu1DPM/G8o0sL3quTe3ckF1D6Qy0ZTnj0IzIjSv U6UZs0KTosBM/DjkrhVetEUHZnhiijHSlcd+w6paThHDffQcazFv3utNj5xgF7fV2uUTDn 27tW3eaQnmmDPxuFsJNeXucE5todNuU=
-
Arc-seal:
i=1; s=arc; d=plant.systems; t=1530698609; a=rsa-sha256; cv=none; b=c4CeHxd5C2d20Tp3Uv+USrV89hiXdsc/AFNycGcGpR6ydkhVONeVsS4nBmqK2iqJtXxybSNOp4X8uPscCOaua9RMkDkZPGKf7rr6gxcGU/HK8JvjrpeA5I+ShxFf13i0fZ8XwiT53ro/PihCr0572PWevmX3Y6lEIl2nky+OdR8=
-
Authentication-results:
ORIGINATING; auth=pass smtp.auth=thomas@plant.systems smtp.mailfrom=thomas@plant.systems
-
User-agent:
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
Hello,
I'd have a question about MariaDB 10.1 replication, which has been
interrupted by a power outage in our datacenter.
We started the master server and had a duplicate id in a table on the
slave, so replication stopped. We did not have time to adjust this at
the moment, there were a lot of other systems to start and check if all
was alright.
Today I had time to look at the error, removed the duplicate ID from the
table and started the slave thread again using 'start slave;'.
But now I get another error:
Last_IO_Error: Got fatal error 1236 from master when reading data from
binary log: 'Error: connecting slave requested to start from GTID
0-2-2948175468, which is not in the master's binlog. Since the master's
binlog contains GTIDs with higher sequence numbers, it probably means
that the slave has diverged due to executing extra erroneous transactions'
Can this be resolved? Or will I have to start replication from scratch?
Greetings,
Thomas
Follow ups
