Re: InnoDB Cluster Distributed Recovery seemingly stuck forever
Posted by:
Raphaël G
Date: May 05, 2021 02:33PM
The secondary node seems to report a GTID set bigger (newer?) than the primary's which could explain why it's waiting for updates if it considers itself "ahead" of the primary. That doesn't make a lot of sense sadly, what scenario could lead a secondary node to have a more recent GTID than the primary ? I decided to disable multithreading appliers (slave_parallel_workers=1) as it wasn't enabled before we updated to 8.0.23, just in case.
mysql> SELECT @@GTID_EXECUTED;
secondary : c86adab9-8573-11eb-bd74-fa163ed5368e:1-14595759
primary : c86adab9-8573-11eb-bd74-fa163ed5368e:1-13588035
Subject
Views
Written By
Posted
1467
April 07, 2021 09:13AM
Re: InnoDB Cluster Distributed Recovery seemingly stuck forever
531
May 05, 2021 02:33PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.