[MXS-3506] SELECT on temporary table fails with "Table doesn't exist" error Created: 2021-04-16 Updated: 2021-04-22 Resolved: 2021-04-21 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Mike Ilin | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | maxscale | ||
| Environment: |
OS Xubuntu 16.04 |
||
| Attachments: |
|
| Description |
|
The problem is specific for MariaDB Galera Cluster, and cannot be reproduced on standalone MariaDB. Steps to reproduce:
2. Execute the statement below in a separate query, but on the same connection:
Result is:
Still it's possible to execute DELETE or INSERT on the temporary table 'ILIN.__ttmp_test_host_product_table' |
| Comments |
| Comment by Jan Lindström (Inactive) [ 2021-04-19 ] | ||||||||||||||||
|
Hi, can you give full example program how to reproduce this? | ||||||||||||||||
| Comment by Mike Ilin [ 2021-04-20 ] | ||||||||||||||||
|
Hi, code fragment is in the attachment. Here is trace fragment corresponding to the code execution:
| ||||||||||||||||
| Comment by Jan Lindström (Inactive) [ 2021-04-20 ] | ||||||||||||||||
|
Hi, thanks but can I really use that code as it uses KLSTD_TRACE and KLSTD_CHECK ? | ||||||||||||||||
| Comment by Mike Ilin [ 2021-04-20 ] | ||||||||||||||||
|
I updated the code in the attachment | ||||||||||||||||
| Comment by Ramesh Sivaraman [ 2021-04-20 ] | ||||||||||||||||
|
Mike Ilin Could not reproduce the issue on my local machine using given program.
| ||||||||||||||||
| Comment by Mike Ilin [ 2021-04-20 ] | ||||||||||||||||
|
@Ramesh Sivaraman perhaps, the problem is caused by Maxscale proxy which is used to redirect queries to Galera nodes. Is it possible that maxscale proxy connects to some other node while running the queries ? | ||||||||||||||||
| Comment by Ramesh Sivaraman [ 2021-04-20 ] | ||||||||||||||||
|
Mike Ilin MaxScale can do read/write splitting with Galera cluster. Please check whether you have enabled read/write splitting in maxscale. | ||||||||||||||||
| Comment by Mike Ilin [ 2021-04-21 ] | ||||||||||||||||
|
Hi ! | ||||||||||||||||
| Comment by Ramesh Sivaraman [ 2021-04-21 ] | ||||||||||||||||
|
Mike Ilin This confirms the issue is due to read/write splitting. Please let us know if you see any other issue. | ||||||||||||||||
| Comment by Mike Ilin [ 2021-04-21 ] | ||||||||||||||||
|
Thanks for the information ! Can I just disable splitting by removing this section from the config file:
or additional settings are required ? | ||||||||||||||||
| Comment by markus makela [ 2021-04-21 ] | ||||||||||||||||
|
Change it from router=readwritesplit to router=readconnroute and add router_options=master to that section. |