[MXS-4966] mariadb-dump gets an error dumping schemas Created: 2024-02-04  Updated: 2024-02-05

Status: Open
Project: MariaDB MaxScale
Component/s: None
Affects Version/s: 23.08.4
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Oli Sennhauser Assignee: markus makela
Resolution: Unresolved Votes: 0
Labels: maxscale, schemarouter
Environment:

Linux n.a.

Issue Links:
Relates
relates to MXS-4947 Tables in information_schema are trea... Closed

 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...

 Comments   
Comment by markus makela [ 2024-02-04 ]

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.

Comment by markus makela [ 2024-02-05 ]

Looking at the SQL being generated by mariadb-dump, I think that MXS-4947 might fix this.

Generated at Thu Feb 08 04:32:26 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.