[kolla] How to recover MariaDB if there's a controller failed to boot?

Eddie Yen missile0407 at gmail.com
Mon Nov 16 10:33:22 UTC 2020

Hi yoctozepto, thanks your advice.

Perhaps need to do maraidb_recovery again once the failure node back online
to prevent brain split issue.
But we'll try it if we met the same case again in the future!

Thank you very much,

Radosław Piliszek <radoslaw.piliszek at gmail.com> 於 2020年11月16日 週一 下午4:04寫道:

> On Mon, Nov 16, 2020 at 3:52 AM Eddie Yen <missile0407 at gmail.com> wrote:
> >
> > Hi everyone,
> >
> Hi Eddie!
> > We met an issue few days ago. When we launch Openstack cluster, we found
> > that there's a controller couldn't boot up caused by hardware failure,
> And MariaDB
> > lost sync after left controllers booted into system.
> > In this case, Can I just mark down the failed controller hostname in
> inventory file and
> > do mariadb_recovery? Any risk after do this after failure one back
> online?
> It is supposed to be used like you are saying.
> As long as the alive controllers have all the data you need, it will work
> fine.
> They should if they were up before failure.
> The failed one will either be unable to rejoin the cluster or just
> follow the others.
> It depends on its local state.
> It will not impose its state on others so it is safe to turn it on and
> then fix it.
> (All the above assumes standard configuration)
> >
> > Many thanks,
> > Eddie.
> -yoctozepto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20201116/45f169da/attachment-0001.html>

More information about the openstack-discuss mailing list