Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
1.2.1, 1.3.0
-
None
Description
I am experiencing issues when doing update to mediumblobs in the database using MaxScale. Issues might also occur when doing inserts, however I am not able to reliably test it at the moment.
The blobs are about 600KB in size.
I verified that the blobs are saved to the database properly. But the application gets weird exceptions on a random basis. Sometimes there can be no exceptions at all.
Issues do not occur when the application is connecting directly to the master database. Reads are working fine regardless of the connection method.
I am attaching snips from application and MaxScale logs. It seems that the blob outputs are truncated.
I am also attaching the database and MaxScale configs. Nothing relevant appears in the database error log.
MariaDB version is 10.1.10.
MaxScale version is 1.2.1.
MaxScale is running on Centos 7, Linux 3.10.0-327.4.5.el7.x86_64 #1 SMP.
Could it be that those issues are somehow connected to the "LONGBLOB are currently not supported" limitation?
Please let me know if there is any more info I could provide to shed more light on this issue.
Attachments
Issue Links
- duplicates
-
MXS-477 readconnroute misinterprets data as COM_CHANGE_USER
- Closed