52b3185a19
In the event of an uncontrolled reboot on a Standard configuration, we were seeing a behavior where the MariaDB pods kept trying to elect a leader and restarting until the pods get to CrashLoopBackoff. After checking the logs closely and reproducing the problem quite easily by deleting both pods at the same time, we came to the conclusion that the cluster wasn't having enough time to elect a new leader and recover from the crash. This patch increases the timeout for the startup probe of the mariadb statefulset with some slack to allow databases that are in production to fully resync the data between the 2 pods. Closes-Bug: #1938346 Signed-off-by: Thiago Brito <thiago.brito@windriver.com> Change-Id: I19e49dab55f3a8661fa71be315093029adb0947e