Is this desync behavior expected?

[Private Citizen]

I setup three nodes in a cluster using MariDB 10.6.4 and Galera-4 26.4.9

I put a value in a table, row, column. Lets say value '1'

Confirmed all 3 nodes show the value as '1'

On node 3 i turned off Galera (wsrep_on=OFF)

Restarted node 3 in stand alone and altered the value from '1' to '2'

I then turned Galera back on (wsrep_on=ON) and restarted.

Node 3 rejoined the cluster, and i was expecting to see the value i changed to '2' be changed back to '1' to be in sync with the cluster.

This did not happen, node 3 stayed '2' while nodes 1 and 2 still showed '1' as the value.

This surprised me as i expected it to sync, either the value '2' be changed to match the cluster, or the cluster change to match the newest edit.

Is this expected behavior?

(If it maters i have dirty reads on.)

[Colin Charles]

Was the node desynced? You can tell from show status of course. It is not expected behaviour, no

--
You received this message because you are subscribed to the Google Groups "codership" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codership-tea...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codership-team/9ac65c54-debd-47ae-b4eb-7a4003a56a8dn%40googlegroups.com.

--

Colin Charles, http://www.bytebot.net/
"First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi

[Private Citizen]

No the node was not desynced. I even did an INSERT and UPDATE query on node 1 to see if while passing those queries around the cluster it would bring node 3 "up to date". It did not. Node 3 showed the two newest queries while still having a desynced value for the one update i did while node 3 was not in wsrep=on mode. I then did an UPDATE on node 1 to the desynced row but for a different column. When node 3 got that query it then showed synced values on all of the columns of that row.