[DRBD-user] 20TB cluster: 1 big drbd disk or multiple small ones?

[Eric Robinson]

> -----Original Message-----
> From: drbd-user-bounces at lists.linbit.com <drbd-user-
> bounces at lists.linbit.com> On Behalf Of Matt Kereczman
> Sent: Monday, June 21, 2021 1:09 PM
> To: drbd-user at lists.linbit.com
> Subject: Re: [DRBD-user] 20TB cluster: 1 big drbd disk or multiple small ones?
>
> On 6/21/21 3:19 AM, Eric Robinson wrote:
> > Suppose you're building a cluster with 20TB of storage that will run
> > multiple instances of MySQL. Which is better, creating one big drbd
> > disk, or carving it up into multiple smaller ones?
>
> Many small DRBD resources is likely better than one large resource in this
> case. With multiple resources you'll have independent failure domains as
> opposed to one large one.

My mind is leaning in the same direction.

>Also, each DRBD resource will get it's own set of
> processes (worker/sender/receiver/etc.) and network socket which will
> likely help with performance.
>

Hmm. Good thought. Had not considered that.

> You could even use, "options { cpu-mask $mask; }", in your DRBD
> configurations to ensure each resource gets it's own CPU thread. Here is a
> link to the relevant section in the DRBD users guide:
> https://linbit.com/drbd-user-guide/drbd-guide-9_0-en/#s-latency-tuning-
> cpu-mask
>
> >
> > Also, any thoughts about a preferred filesystem for this scenario?
> <snip>
> Any journaling FS (xfs/ext4) mounted with noatime should be fine.
>

Not xfs then?

> Best Regards,
> Matt
> _______________________________________________
> Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list drbd-
> user at lists.linbit.com https://lists.linbit.com/mailman/listinfo/drbd-user
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.