Anyone did maria db upgrade to 10.6 with galera cluster? I see this: https://mariadb.com/kb/en/upgrading-from-mariadb-103-to-mariadb-104-with-galera-cluster/
but I am unable to find a document for upgrade to 10.6 with Galera. Wondering if its stable to do a 10.6 galera upgrade.
Thanks
Related
I am upgrading my galera mariadb cluster from mariadb -10.3 to mariadb 10.6. I am trying to start a new cluster : sudo /usr/bin/galera_new_cluster . I see an error ,
[ERROR] WSREP: It may not be safe to bootstrap the cluster from this node. It was not the last one to leave the cluster and may not contain all the updates. To force cluster bootstrap with this node, edit the grastate.dat file manually and set safe_to_bootstrap to 1 .
I am seeing references to set the variable safe_to_bootstrap to 1 in /var/lib/mysql/grastate.dat.
There is no such file grastate.dat in the directory in any of my cluster nodes. This is one of my qa servers. Any pointers if I can create one file new?
Thanks
So I used to have mysql installed on my mac via homebrew. I stared by uninstalling it and then installed maria with brew install mariadb
This shows me this version
> mysql --version
mysql Ver 15.1 Distrib 10.7.3-MariaDB, for osx10.17 (arm64) using EditLine wrapper
and this:
mariadb --version
mariadb Ver 15.1 Distrib 10.7.3-MariaDB, for osx10.17 (arm64) using EditLine wrapper
I can run mariadb and connect to it fine with this command:
mariadb -u root -p
However, I am not able to use the new feature of mariaDB called system versioned tables.
I have followed this guide: https://mariadb.com/kb/en/system-versioned-tables/ and entered this command
MySQL [(none)]> CREATE TABLE t ( x INT ) WITH SYSTEM VERSIONING;
Which gives this error:
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'SYSTEM VERSIONING' at line 1
To test this further, I created a MariaDB instance in aws and connected to it locally with the same command which works fine. The version that RDS supports is 10.6
Question: "Why can't does my local instance of mariadb not recognize the keyword SYSTEM?
I am not sure how to debug this locally and I would like to know why this version of mariadb is unable to recognize these command locally. Looking for some debugging tips.
EDIT: Another thing to check was to select version while in the mariadb console
MySQL [(none)]> select version();
+-----------+
| version() |
+-----------+
| 8.0.28 |
+-----------+
8.0.28 is a MySQL version, which doesn't have System Versioned Tables, only MariaDB does (at the time of this posting anyway).
As noted, mysql --version only shows the version of the MySQL (or MariaDB via compatibility links) client. It doesn't show the server version.
We have a MySQL task that is connecting to a 5.7.22 MySQL DB just fine in Airflow 1.10.15 using SSL (Extra: {"ssl": {"ca": "ca.pem"}} ). However, once we upgraded to Airflow 2.0.2 the task fails with (2026, 'SSL connection error: error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol'). Does anyone have any ideas about this behavior?
Below are the python packages for both before and after
Airflow 1.10.15
mysqlclient==1.3.14
Airflow 2.0.2
mysql-connector-python==8.0.22
mysqlclient==2.0.3
I think the problem might be because Airflow 2 uses a newer Debian which does not support TLS v1.
I am not 100% sure how you should configure your MySQL/Client but this sounds awfully similar to MySQL ERROR 2026 - SSL connection error - Ubuntu 20.04
The solution is either to disable SSL (not recommended) or decrease security level of Debian (not recommended) or make sure that you use TLS v2
Apparently this can be done via changing your MySQL seetings and restarting it:
[mysqld]
tls_version=TLSv1.2
I install a laragon on my windows 10 and using the latest mariadb database
Ver 15.1 Distrib 10.2.12-MariaDB, for Win64 (AMD64)
but when I try to connect using this command
mysql -u root -p
I received this error
ERROR 2002 (HY000): Can't connect to MySQL server on 'localhost' (10061)
What is this error?
I don't know what to do.
When you install MariaDB, by default it creates a database called "mysql".
If you delete that database, that exact error will appears. The solution is either recover that database or reinstall mariadb. I spent one day figuring out why does that error appeared to me.
Conclusion: Don't delete "mysql" database from mariadb.
i wanted to increase the value of gcache.size on my 3 nodes of the mariadb galera cluster (galera v25.3.22(r3764), mariadb Ver 15.1 Distrib 10.0.33 -
MariaDB, for Linux (x86_64) using readline 5.1), from the standard 128MB to 1G.
I have sufficient space on my disk.
I shutdown all 3 nodes, change the parameter in the my.cnf:
wsrep_provider_options="gcache.size=1G"
restart the nodes, but the size stays same (on disk as in the wsrep_provider_options).
is this a bug?
I can for example change these 2 parameters without problem:
wsrep_provider_options="gcache.recover=yes"
wsrep_provider_options="gcache.page_size=1G"
but the gcache.size doesnt increase