Browse Source
In a DX scenario, after lock-unlock a controller the remaining MariaDB instance (lets say maria-server0) goes to a Non-Primary + Initializing State (non-operational). After that it remains searching for the now deleted pod (maria-server1) but using the old IP, the one before the restart. maria-server0 flags the old IP as delayed and suspect for eviction, however being a Non-Primary member it cannot in fact evict the old node and start looking for new members. Setting a LivenessProbe that detects nonoperational members and restart them fixes this, as the recreated pod starts looking for a cluster to join. Closes-Bug: #1938346 Signed-off-by: Thiago Brito <thiago.brito@windriver.com> Change-Id: I38d788f720cbd6bd13b6b6147db6f3d2a2ff9c92changes/96/803096/2
2 changed files with 15 additions and 5 deletions
Loading…
Reference in new issue