[ClusterLabs] Antw: [EXT] Custom RA for Multi-Tenant MySQL?

Eric Robinson eric.robinson at psmnv.com
Tue Apr 13 01:20:31 EDT 2021


> -----Original Message-----
> From: Users <users-bounces at clusterlabs.org> On Behalf Of Ulrich Windl
> Sent: Monday, April 12, 2021 2:37 AM
> To: users at clusterlabs.org
> Subject: [ClusterLabs] Antw: [EXT] Custom RA for Multi-Tenant MySQL?
>
> >>> Eric Robinson <eric.robinson at psmnv.com> schrieb am 11.04.2021 um
> >>> 19:07 in
> Nachricht
> <SA2PR03MB588472C22F1D76CC21FB0F67FA719 at SA2PR03MB5884.namprd0
> 3.prod.outlook.com>
>
> > We're writing a custom RA for a multi‑tenant MySQL cluster that runs
> > in active/standby mode. I've read the RA documentation about what exit
> > codes should be returned for various outcomes, but something is still
> > unclear to me.
> >
> > We run multiple instances of MySQL from one filesystem, like this:
> >
> > /app_root
> >                 /mysql1
> >                 /mysql2
> >                 /mysql3
> >                 ...etc.
> >
> > The /app_root filesystem lives on a DRBD volume, which is only mounted
> > on the active node.
> >
> > When the RA performs a "start," "stop," or "monitor" action on the
> > standby node, the filesystem is not mounted so the mysql instances are
> not present.
>
> > What should the return  codes for those actions be? Fail? Not installed?
> > Unknown error?
>
> If the DB needs the FS, and the FS is not there, the DB cannot be running, so
> monitor would report "stopped", stop would report success, and star woulkd
> report failure.
>

Under what conditions would you want to report "Unknown Error?"

> >
> >
> > [email_sig]
> >
> > Disclaimer : This email and any files transmitted with it are
> > confidential and intended solely for intended recipients. If you are
> > not the named addressee you should not disseminate, distribute, copy or
> alter this email.
>
> > Any views or opinions presented in this email are solely those of the
> > author
>
> > and might not represent those of Physician Select Management. Warning:
> > Although Physician Select Management has taken reasonable precautions
> > to ensure no viruses are present in this email, the company cannot
> > accept responsibility for any loss or damage arising from the use of
> > this email or
>
> > attachments.
>
>
>
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.


More information about the Users mailing list