Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
23.08.4
-
Linux n.a.
Description
If I run the mariadb-dump command via MaxScale I get an error on all Schemas which are NOT located on the first shard:
mariadb-dump --user=app --password=secret --host=10.153.125.219 --port=3306 --single-transaction customer_0010 > /tmp/customer_0010.sql
mariadb-dump --user=app --password=secret --host=10.153.125.219 --port=3306 --single-transaction customer_0020 > /tmp/customer_0020.sql
Error: Couldn't read status information for table address ()
Error: Couldn't read status information for table sales ()
mariadb-dump --user=app --password=secret --host=10.153.125.219 --port=3306 --single-transaction customer_0030 > /tmp/customer_0030.sql
Error: Couldn't read status information for table address ()
Error: Couldn't read status information for table sales ()
mariadb-dump --user=app --password=secret --host=10.153.125.219 --port=3306 --single-transaction --databases customer_0011 > /tmp/customer_0011.sql
mariadb-dump --user=app --password=secret --host=10.153.125.219 --port=3306 --single-transaction --databases customer_0021 > /tmp/customer_0021.sql
Error: Couldn't read status information for table address ()
Error: Couldn't read status information for table sales ()
mariadb-dump --user=app --password=secret --host=10.153.125.219 --port=3306 --single-transaction --databases customer_0030 > /tmp/customer_0030.sql
Error: Couldn't read status information for table address ()
Error: Couldn't read status information for table sales ()
customer_001? are on the first shard customer_002? on the second and so on...
I did not find anything in the docu prohibiting this...
Attachments
Issue Links
- relates to
-
-
- Closed
-
Activity
Looking at the SQL being generated by mariadb-dump, I think that MXS-4947 might fix this.
I'll close this as a duplicate of MXS-4947. If you can, please retry this with the MaxScale 23.08.5 release once it's out.
This could be some interaction between how things like SHOW DATABASES and SHOW TABLES IN <db> are processed by the schemarouter. I'll try and reproduce this locally.