Build tested: 23.02

engine: 7d812b1b7e33d9700882b111be62e38a58e54e4d
server: bf7f6987c8fb7ceda9ae048ada129d11798d4392
buildNo: 6164

The module ID is in /var/lib/columnstore/local/module in each node. After initial installation and before failover, the module ID in each node matches Maxscale status.

columnstore: mcs1=pm1, Maxscale: server=pm1 Address=mcs1
columnstore: mcs2=pm2, Maxscale: server=pm2 Address=mcs2
columnstore: mcs3=pm3, Maxscale: server=pm3 Address=mcs3

Maxscale, ColumnStore matched

After failover completed (stop container mcs1, mcs2 became the primary node, start mcs1)

columnstore: mcs1=pm3, Maxscale: server=pm1 Address=mcs1
columnstore: mcs2=pm1, Maxscale: server=pm2 Address=mcs2
columnstore: mcs3=pm2, Maxscale: server=pm3 Address=mcs3

Please note that ColumnStore's module ID changed, not matching with Maxscale.
Release 22.08.4 does not have this issue.

This is different from MCOL-4763. In MCOL-4763, Columnstore's node ID does not match the address column from Maxscale.