Hello,
for the records: after upgrading to 10.11.6 from the project repo the
error is gone and sync is stable for more than two weeks now.
Oliver
On 16.01.24 13:36, Oliver Welter via discuss wrote:
Hello Marko,
thanks for the fast reply - the test with the rebuild were done with
10.11.5 taken from Debaian unstable as I had to grab them earlier last
year when I got hit by https://jira.mariadb.org/browse/MDEV-30531
after upgrading to bookworm. To have a clean state to start from I
rolled this back two weeks ago but this time I used a binary copy from
the master.
I will follow your suggesting and prepare a new machine using the
project repositories and will report back my findings.
Thanks so far
Oliver
On 16.01.24 10:20, Marko Mäkelä via discuss wrote:
Hi Oliver,
It is good that you can reproduce this after rebuilding the replica
from a logical SQL dump. Was everything done on MariaDB Server
10.11.4? There are several bugs that could explain this corruption
that have been fixed since the release of MariaDB Server 10.11.4.
These include MDEV-32530, MDEV-31767 and MDEV-30531. Can you reproduce
this corruption after upgrading to 10.11.6?
Best regards,
Marko
_______________________________________________
discuss mailing list -- [email protected]
To unsubscribe send an email to [email protected]
--
Protect your environment - close windows and adopt a penguin!
_______________________________________________
discuss mailing list -- [email protected]
To unsubscribe send an email to [email protected]
