[MXS-2268] readwritesplitter is not routing queries properly in Maxscale 2.3.2 - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 2.3.2
Fix Version/s: 2.2.20, 2.3.4
Component/s: readwritesplit
Labels:
None
Environment:
CentOS 7, Rackspace cloud using OnMetal servers. Percona MySQL 5.6 behind Maxscale and PHP application in front.

Description

Upon installing and configuring MaxScale 2.3.2 we encountered errors when slave database (which has read_only=1 set). After investigating it looks like MaxScale is marking all queries as read queries. We have a previous installation running version 2.1.11 which we never saw this issue on. Not a single query was marked as write despite the write queries being simple inserts. Attached is a log that contains queries showing that they are flagged as read.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

maxscale.cnf
2019-01-17 03:06
2 kB
Jeffrey Parker
maxscale-minimal.cnf
2019-02-04 21:47
2 kB
Jeffrey Parker
querysample_maxscale.log.gz
2019-01-16 19:53
14 kB
Jeffrey Parker
test_insert1.sql
2019-02-04 21:47
0.1 kB
Jeffrey Parker

Issue Links

is duplicated by

MXS-2270 MaxScale 2.3 readwritesplit will not route temporary tables to master with leading comments

Closed

Activity

People

Assignee:: markus makela

Reporter:: Jeffrey Parker

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2019-01-16 19:53

Updated:: 2019-02-08 07:38

Resolved:: 2019-02-08 07:37

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.