1 |
Bug: https://bugs.gentoo.org/825234 |
2 |
Signed-off-by: Thomas Deutschmann <whissi@g.o> |
3 |
--- |
4 |
...adb-database-restore-maybe-required.en.txt | 45 +++++++++++++++++++ |
5 |
1 file changed, 45 insertions(+) |
6 |
create mode 100644 2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt |
7 |
|
8 |
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 |
9 |
new file mode 100644 |
10 |
index 0000000..5d8afda |
11 |
--- /dev/null |
12 |
+++ b/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt |
13 |
@@ -0,0 +1,45 @@ |
14 |
+Title: Full MariaDB database restore maybe required |
15 |
+Author: Thomas Deutschmann <whissi@g.o> |
16 |
+Posted: 2021-11-23 |
17 |
+Revision: 1 |
18 |
+News-Item-Format: 2.0 |
19 |
+Display-If-Installed: dev-db/mariadb |
20 |
+Display-If-Installed: sys-cluster/galera |
21 |
+ |
22 |
+On 2021-11-21, keywords for dev-db/mariadb:10.6 were removed to |
23 |
+address a file collision with dev-db/mariadb-connector-c. This |
24 |
+unintentionally triggered a version downgrade for users who had |
25 |
+successfully upgraded to dev-db/mariadb:10.6 already. [Link 1]. |
26 |
+ |
27 |
+However, downgrades are not supported in MySQL/MariaDB [Link 2]. |
28 |
+ |
29 |
+In case you already fully upgraded to MariaDB 10.6 (which includes |
30 |
+executing mysql_upgrade command) and unintentionally downgraded your |
31 |
+MariaDB instance afterwards during the time window when keywords were |
32 |
+removed, you maybe experiencing different problems: |
33 |
+ |
34 |
+At best, your unwanted downgraded MariaDB instance prevented startup |
35 |
+so all you have to do is upgrade to MariaDB 10.6 again to resume |
36 |
+services. |
37 |
+ |
38 |
+In case previous MariaDB version was able to start, you are encouraged |
39 |
+to do a full backup as soon as possible using mysqldump command and |
40 |
+manually restore each database ("logical downgrade") to prevent any |
41 |
+data corruption. |
42 |
+ |
43 |
+Depending on used feature set and from which version you upgraded, |
44 |
+it is maybe required to do a full restore from a previous backup before |
45 |
+MariaDB 10.6 upgrade to restore services and prevent any data loss or |
46 |
+future runtime errors. |
47 |
+ |
48 |
+In case you are using MariaDB in a cluster and/or Galera setup you |
49 |
+probably have to rebuild the entire cluster in case the upgrade to |
50 |
+MariaDB 10.6 was already replicated (using pt-table-checksum from |
51 |
+dev-db/percona-toolkit can help you to validate your cluster). |
52 |
+ |
53 |
+Keep in mind that due to the forced downgraded, point-in-time recovery |
54 |
+may not be available to the extent that you are used to. |
55 |
+ |
56 |
+Link 1: https://bugs.gentoo.org/825234 |
57 |
+ |
58 |
+Link 2: https://mariadb.com/kb/en/downgrading-between-major-versions-of-mariadb/ |
59 |
-- |
60 |
2.34.0 |