[MXS-2270] MaxScale 2.3 readwritesplit will not route temporary tables to master with leading comments Created: 2019-01-16 Updated: 2019-02-11 Resolved: 2019-02-11 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readwritesplit |
| Affects Version/s: | 2.3.2 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Critical |
| Reporter: | Dave Juntgen | Assignee: | markus makela |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Centos 6 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
| Comments |
| Comment by Dave Juntgen [ 2019-01-17 ] | ||||||||||||||||||||||
|
I should note that the SQL was delivered via the mysql C API with MYSQL_OPTION_MULTI_STATEMENTS_ON. When running the SQL from the command line, the results are not the same. C code is as such: mysql_set_server_option(conn,MYSQL_OPTION_MULTI_STATEMENTS_ON); | ||||||||||||||||||||||
| Comment by Dave Juntgen [ 2019-01-17 ] | ||||||||||||||||||||||
|
Please see the attach C problem presents the problem. Basically, it comes down to the following: Broken Comment before creating table stmt
MaxScale Log
Working Query
MaxScale Log of working log
| ||||||||||||||||||||||
| Comment by markus makela [ 2019-01-18 ] | ||||||||||||||||||||||
|
We can see that the broken query has been somehow transformed into a single-line entry which of course comments out the whole statement. The parser sets the type of comments as READ which should explain why they end up going to the master. Can you try and see if it works without the filters? | ||||||||||||||||||||||
| Comment by markus makela [ 2019-01-18 ] | ||||||||||||||||||||||
|
I took a look at your example code and it doesn't add newlines after the statement. Try adding \n before each backslash that terminates a line the query string. | ||||||||||||||||||||||
| Comment by markus makela [ 2019-01-18 ] | ||||||||||||||||||||||
|
If possible, please try and see if adding query_classifier_cache_size=0 in the [maxscale] section helps. | ||||||||||||||||||||||
| Comment by markus makela [ 2019-02-06 ] | ||||||||||||||||||||||
|
If possible, please read this comment here: https://jira.mariadb.org/browse/MXS-2268?focusedCommentId=123004&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-123004 | ||||||||||||||||||||||
| Comment by markus makela [ 2019-02-06 ] | ||||||||||||||||||||||
|
You can ignore the comment I made earlier, we've found a bug that is quite likely to cause this problem. We built packages with the fix which can be found here: http://max-tst-01.mariadb.com/ci-repository/MXS-2268/mariadb-maxscale/ | ||||||||||||||||||||||
| Comment by markus makela [ 2019-02-11 ] | ||||||||||||||||||||||
|
Closing as a duplicate now that the real cause of | ||||||||||||||||||||||
| Comment by Dave Juntgen [ 2019-02-11 ] | ||||||||||||||||||||||
|
Thank you! |