The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-16. For the latest, interactive version please visit https://mariadb.com/kb/.

install_spider.sql: no xa?

I've a fresh server with MariaDB on it. After running install_spider.sql into it, the result of "SELECT engine, xa FROM information_schema.engines;" is:

+--------------------+------+
| engine             | xa   |
+--------------------+------+
| SPIDER             | NO   |
| MRG_MyISAM         | NO   |
| MEMORY             | NO   |
| BLACKHOLE          | NO   |
| MyISAM             | NO   |
| InnoDB             | YES  |
| ARCHIVE            | NO   |
| FEDERATED          | NO   |
| PERFORMANCE_SCHEMA | NO   |
| Aria               | NO   |
| CSV                | NO   |
+--------------------+------+

According to KB, this isn't meant to look like this and instead I'm meant to have xa set to YES on SPIDER. I'm running MariaDB 10.0.16 and here's my install_spider.sql: http://pastebin.com/RzrWTpaQ

So the question is, why isn't xa being enabled on SPIDER?

Answer Answered by Sergei Golubchik in this comment.

MariaDB cannot enable XA at runtime. If you have binlogging disabled and less than two XA-capable engines loaded, then all XA support code in the server is completely disabled. And if you load a new XA-capable engine, its XA capabilities will be disabled until you restart MariaDB.

There is a warning about disabled XA when you install the engine, but as you have the "INSTALL PLUGIN" statement buried deep inside your install_spider.sql script, you must've missed it.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.