This happens when you have a Spider table defined that does not point to an existing table on a data node.
myisam-recover=FORCE,BACKUP
optimizer_switch='engine_condition_pushdown=on'
When using join_cache_level = 6 to get faster joins on the network it is recommended to use :
optimizer_switch='mrr=on,mrr_sort_keys=off'
see : MDEV-5976
This is used by Spider monitoring to ask other monitoring nodes the status of a table.
Not having a primary key will generate errors for resynchronizing tables via spider_copy_table().
Yes, XA transactions can be disabled from Spider. Until Galera 4.0 fully supports xa transactions, spider can point to a maxscale proxy that can manage transparent node election in case of failure inside a shard group. Note that disabling XA will break cross shard WRITES in case of transaction ROLLBACK. This architecture need to be used with care if you have a highly transactional workload that can generate cross shard deadlocks.
© 2019 MariaDB
Licensed under the Creative Commons Attribution 3.0 Unported License and the GNU Free Documentation License.
https://mariadb.com/kb/en/spider-faq/