[MXS-1219] MaxScale statements and Online DDL Created: 2017-04-13  Updated: 2017-05-18  Resolved: 2017-05-18

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbbackend, mariadbclient
Affects Version/s: 1.4.4
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Oren Bissick (Inactive) Assignee: Massimiliano Pinto (Inactive)
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

CentOS 7, MariaDB 10.1

Sprint: 2017-32, 2017-33

 Description   

MaxScale connections waiting when performing Online DDL.

 Comments   
Comment by Oren Bissick (Inactive) [ 2017-04-20 ]

Using maxscale version 1.4, using readwrite split router.
example:
if i run: ALTER ONLINE TABLE tablename ROW_FORMAT=COMPRESSED;
i saw that queries sent through MaxScale router was just sitting there waiting on alter to complete.

Comment by Massimiliano Pinto (Inactive) [ 2017-04-24 ]

Hi, do you see the same when issuing the ALTER ONLINE TABLE directly in the master database?

Are you using MySQL/MariADB client or any special connector?

Would you mind adding the output of mysql client for both direct connection and maxscale connection when issuing ALTER ONLINE TABLE?

Thanks.

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