Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
None
-
2022-22
Description
Build tested: 22.08.2, latest build from drone (#5838)
Steps:
1. Create a 3PM docker cluster
2. Check cluster status on PM1. master=PM1, slave=PM2, PM3
3. Create a database and a table, insert a row in PM1
4. Verify table gets replicated to PM2
5. Execute "docker container stop mcs1", wait 90 seconds
6. Execute "docker container start mcs1", wait 60 seconds
7. Check cluster status on PM1. master=PM1, slave=PM2, PM3
Yesterday, I noticed MaxScale had PM2 sat as the master
Today, MaxScale also set PM1 as the master (I don't know why such behavior today)
For this test, PM2 was expected to take over as the master
8. Create another table and inserted a row on PM1
9. The table did not get replicated to PM2 or PM3
10. "show slave status" on PM2 returned nothing
11. "show slave status" on PM3 did return status, and no error
PM3 slave status showed master log mariadb-bin.000002, position 4684
PM1 master status showed master log mariadb-bin.000004, position 568
Attachments
Issue Links
- is blocked by
-
MCOL-5306 Broken connections in mariadb while primary node down. failover related.
- Closed
- relates to
-
MCOL-5286 HA Failing when losing a node - restart secondary - pm3
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...