Comment 9 for bug 1989505

@Nishant, that is a valid workaround, until you add/remove another unit and hit the problem again. The best way to overcome the problem and avoid it repeating itself is to move unit leadership back to the lowest numbered unit. In your example it is mysql-innodb-cluster/0. This way the relation-data that will be read will be the one maintained by the leader. If leadership changes again, you just have to move it back to lowest numbered unit.