[MXS-3907] Unexpected result state Created: 2021-12-09  Updated: 2021-12-10  Resolved: 2021-12-10

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: 6.2.0
Fix Version/s: 6.2.1

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

Xpand 5.3.18


 Description   

This appeared during testing with a custom MaxScale build. Does not happen with MaxScale 2.5.14, most likely a result of 6.2.0.

2021-12-08 21:22:18   error  : (79) Unexpected result state. cmd: 0x08, len: 41 server: @@Xpand-Monitor:node-15
 
2021-12-08 21:22:18   error  : (79) Unexpected result state. cmd: 0xfe, len: 5 server: @@Xpand-Monitor:node-15
 
2021-12-08 21:22:18   error  : (81) Unexpected result state. cmd: 0x08, len: 41 server: @@Xpand-Monitor:node-1
 
2021-12-08 21:22:18   error  : (81) Unexpected result state. cmd: 0xfe, len: 5 server: @@Xpand-Monitor:node-1
 
2021-12-08 21:22:18   error  : (82) Unexpected result state. cmd: 0x08, len: 41 server: @@Xpand-Monitor:node-13



 Comments   
Comment by markus makela [ 2021-12-09 ]

This might be caused by the addition of the DEPRECATE_EOF and METADATA_CACHE capabilities to the protocol.

Comment by markus makela [ 2021-12-10 ]

The reason was the mismatch between the capabilities declared by MaxScale and the ones supported by the backend databases.

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