[MXS-2461] Unexpected internal state with ReadWriteSplit and proxy_protocol=true Created: 2019-04-30  Updated: 2019-06-17  Resolved: 2019-06-17

Status: Closed
Project: MariaDB MaxScale
Component/s: galeramon, Protocol, readwritesplit
Affects Version/s: 2.3.4
Fix Version/s: 2.3.9

Type: Bug Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
is caused by MXS-2563 Failing debug assertion at rwsplitses... Closed
Relates
relates to MXS-2464 Crash in route_stored_query with Read... Closed
relates to MXS-1760 Adding use_sql_variables_in=master re... Closed
relates to MXS-2066 Result buffering is not always disabled Closed
relates to MXS-2072 [readwritesplit] Unexpected internal ... Closed
relates to MXS-2311 connection_keepalive and error : (485... Closed
Sprint: MXS-SPRINT-82, MXS-SPRINT-83, MXS-SPRINT-84

 Description   

A user started seeing periodic errors like the following in MaxScale 2.3.4:

2019-04-26 07:30:00   error  : (7395) Unexpected internal state: received response 0x00 from server 'mariadb1' when no response was expected. Command: 0x03 Query: <not available>
2019-04-26 19:00:00   error  : (12174) Unexpected internal state: received response 0x2c from server 'mariadb1' when no response was expected. Command: 0x03 Query: <not available>
2019-04-26 19:00:00   error  : (12174) Unexpected internal state: received response 0x03 from server 'mariadb1' when no response was expected. Command: 0x03 Query: <not available>
2019-04-29 01:07:46   error  : (33679) Unexpected internal state: received response 0x00 from server 'mariadb1' when no response was expected. Command: 0x03 Query: <not available>
...
2019-04-29 13:00:00   error  : (38409) Unexpected internal state: received response 0x00 from server 'mariadb1' when no response was expected. Command: 0x03 Query: select * from ...
2019-04-29 13:00:00   error  : (38409) Unexpected internal state: received response 0x00 from server 'mariadb1' when no response was expected. Command: 0x03 Query: select * from ...
2019-04-29 18:08:08   error  : (40715) Unexpected internal state: received response 0x09 from server 'mariadb2' when no response was expected. Command: 0x03 Query: <not available>
2019-04-29 18:32:44   error  : (40212) Unexpected internal state: received response 0x00 from server 'mariadb1' when no response was expected. Command: 0x03 Query: <not available>
2019-04-29 18:32:44   error  : (40212) Unexpected internal state: received response 0x00 from server 'mariadb1' when no response was expected. Command: 0x03 Query: <not available>
2019-04-29 18:32:44   error  : (40212) Unexpected internal state: received response 0x00 from server 'mariadb1' when no response was expected. Command: 0x03 Query: <not available>

The user is using ReadWriteSplit with GaleraMon:

[Galera-Monitor]
type=monitor
module=galeramon
servers=mariadb1,mariadb2,mariadb3
user=mariadb
password=[redacted]
available_when_donor=true
monitor_interval=100
 
[Galera-Service]
type=service
router=readwritesplit
servers=mariadb1,mariadb2,mariadb3
user=mariadb
password=[redacted]
master_accept_reads=true
master_failure_mode=fail_on_write
master_reconnection=true
delayed_retry=true
delayed_retry_timeout=1
max_sescmd_history=200
prune_sescmd_history=true
 
[Galera-Listener]
type=listener
service=Galera-Service
protocol=MariaDBClient
port=3306

And the servers have proxy_protocol=true set:

[mariadb1]
type=server
address=mariadb1.domain.com
port=3306
protocol=MariaDBBackend
proxy_protocol=true



 Comments   
Comment by markus makela [ 2019-05-02 ]

Please try the latest 2.3 release and see if that solves it. Also if it's possible, please try and see if disabling proxy_protocol affects the frequency of the errors.

Comment by markus makela [ 2019-06-17 ]

Possibly caused by MXS-2563, closing as Fixed until more information is available.

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