Gentoo Archives: gentoo-dev

From: Georgy Yakovlev <gyakovlev@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [PATCH] 2021-11-23-mariadb-database-restore-maybe-required: add item
Date: Thu, 25 Nov 2021 10:11:19
Message-Id: 20211125101108.iaqota5dwvrmbyoi@cerberus
In Reply to: [gentoo-dev] [PATCH] 2021-11-23-mariadb-database-restore-maybe-required: add item by Thomas Deutschmann
1 On 25.11.2021 04:21, Thomas Deutschmann wrote:
2 > Bug: https://bugs.gentoo.org/825234
3 > Signed-off-by: Thomas Deutschmann <whissi@g.o>
4 > ---
5 > ...adb-database-restore-maybe-required.en.txt | 46 +++++++++++++++++++
6 > 1 file changed, 46 insertions(+)
7 > create mode 100644 2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt
8 >
9 > diff --git a/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt b/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt
10 > new file mode 100644
11 > index 0000000..c4a698e
12 > --- /dev/null
13 > +++ b/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt
14 > @@ -0,0 +1,46 @@
15 > +Title: Full MariaDB database restore maybe required
16 > +Author: Thomas Deutschmann <whissi@g.o>
17 > +Posted: 2021-11-23
18 > +Revision: 1
19 > +News-Item-Format: 2.0
20 > +Display-If-Installed: dev-db/mariadb
21 > +Display-If-Installed: sys-cluster/galera
22 > +
23 > +On 2021-11-21, a member of the QA project accidentially de-keyworded
24 Agreed with others in the thread, this is not professional.
25
26 > +MariaDB 10.6 to address a file collision, users, who also had latest
27 > +dev-db/mariadb-connector-c installed, experienced (NOTE: The default
28 > +MySQL connector in Gentoo Linux is provided by
29 > +dev-db/mysql-connector-c) [Link 1].
30 This ^ is a very confusing sentence and is way too long. Needs shortening and
31 re-wording, too much commas.
32
33 > +
34 > +However, downgrades are not supported in MySQL/MariaDB [Link 2].
35 > +
36 > +In case you already fully upgraded to MariaDB 10.6 (which includes
37 > +executing mysql_upgrade command) and forcefully downgraded your
38 > +MariaDB instance afterwards during the time window when keywords were
39 > +removed, you maybe experiencing different problems:
40 > +
41 > +At best, your forcefully downgraded MariaDB instance prevented startup
42 > +so all you have to do is upgrade to MariaDB 10.6 again to resume
43 > +services.
44 > +
45 > +In case previous MariaDB version was able to start, you are encouraged
46 > +to do a full backup as soon as possible using mysqldump command and
47 > +manually restore each database ("logical downgrade") to prevent any
48 > +data corruption.
49 > +
50 > +Depending on used feature set and from which version you upgraded,
51 > +it is maybe required to do a full restore from a previous backup before
52 > +MariaDB 10.6 upgrade to restore services and prevent any data loss or
53 > +future runtime errors.
54 > +
55 > +In case you are using MariaDB in a cluster and/or Galera setup you
56 > +probably have to rebuild the entire cluster in case the upgrade to
57 > +MariaDB 10.6 was already replicated (using pt-table-checksum from
58 > +dev-db/percona-toolkit can help you to validate your cluster).
59 > +
60 > +Keep in mind that due to the forced downgraded, point-in-time recovery
61 > +may not be available to the extent that you are used to.
62 > +
63 > +Link 1: https://bugs.gentoo.org/825234#c8
64 > +
65 > +Link 2: https://mariadb.com/kb/en/downgrading-between-major-versions-of-mariadb/
66 > --
67 > 2.34.0
68 >
69 >
70
71 --
72 Best regards,
73 Georgy