Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
2.5.13
-
None
-
MXS-SPRINT-136
Description
We found this error in MaxScale logs while running xpand parallel replication via MaxScale. This looks simillar to MXS-3248 but it does not appear fixed for xpandmon.
[root@karma075 ~]# maxscale -version
|
MaxScale 2.5.13
|
Error:
2021-06-30 15:23:58 error : (7) Unexpected result state. cmd: 0x00, len: 28 server: @@XpandMonitor:node-3
|
2021-06-30 15:23:58 error : (6) Unexpected result state. cmd: 0x00, len: 28 server: @@XpandMonitor:node-5
|
2021-06-30 15:23:58 error : (11) Unexpected result state. cmd: 0x00, len: 28 server: @@XpandMonitor:node-2
|
2021-06-30 15:23:58 error : (13) Unexpected result state. cmd: 0x00, len: 28 server: @@XpandMonitor:node-1
|
2021-06-30 15:23:58 error : (2) Unexpected result state. cmd: 0x00, len: 107 server: @@XpandMonitor:node-3
|
2021-06-30 15:23:58 error : (2) Unexpected result state. cmd: 0x00, len: 28 server: @@XpandMonitor:node-3
|
As mentioned in MXS-3248, this error does not appear when we add connection_keepalive=0s to the readconroute service in maxscale.cnf.