Page MenuHomePhabricator

Build 10.6.22 and 10.11.13 with mdev36934 patch
Closed, ResolvedPublic

Description

After reporting the semi sync bug https://jira.mariadb.org/browse/MDEV-36934 Kristian has generated a patch that it is believed to address the issue. I will repackage our 10.6.22 and 10.11.13 with it applied and will test it.

10.6: commit ce9ee7e78633c9b2568fd9a6fb2b3e2559ea1ba6, branch knielsen-mdev36934-10.6: https://github.com/MariaDB/server/commits/knielsen-mdev36934-10.6
10.11: commit fb33f10321aa9fab1fa81ed1309bda220a703f20, branch knielsen-mdev36934-10.11: https://github.com/MariaDB/server/commits/knielsen-mdev36934-10.11
  • 10.6.22
  • 10.11.13

Related Objects

Event Timeline

Marostegui updated the task description. (Show Details)

Change #1161459 had a related patch set uploaded (by Marostegui; author: Marostegui):

[operations/software@master] control-mariadb-10.6-bookworm: New version

https://gerrit.wikimedia.org/r/1161459

Change #1161459 merged by jenkins-bot:

[operations/software@master] control-mariadb-10.6-bookworm: New version

https://gerrit.wikimedia.org/r/1161459

10.11.13 has been packaged
Moving onto 10.6.22 now

Installed 10.11.13 on db2186 and db2196 in preparation for the switchover T397419

Installed 10.6.22 on db2215 in preparation for the switchover T397419

Change #1161802 had a related patch set uploaded (by Marostegui; author: Marostegui):

[operations/software@master] control-mariadb-10.11-bookworm: New version

https://gerrit.wikimedia.org/r/1161802

Change #1161802 merged by jenkins-bot:

[operations/software@master] control-mariadb-10.11-bookworm: New version

https://gerrit.wikimedia.org/r/1161802

Installed on es2035 and es2037 for the switchover T397597

I switched over x1 for T397419 and I ran into no issues. It is of course early to saw as we don't always have them.

m5 was fine too, although mX normally haven't had issues with semi sync in the past. T397413

Installed on s1 codfw hosts for T398014 (db2203, db2212)

x1 switchover went smooth with the patches applied.

s2 primary switchover: T396976 went fine too with both hosts patched.