大网数据广告活动
服务器运维问答

drbd: quorum and dual primary for ocfs2 without fencing?

· 52CE 我爱测

Due to cephs poor performance on NVME i'm experimenting with OCFS2 on DBRD again. DBRD appears to initially have been built around the idea notifying an application of a hardware failure, and the application taking appropriate st…

问题原文

原帖链接 · aep · CC BY-SA 4.0

Due to cephs poor performance on NVME i'm experimenting with OCFS2 on DBRD again.

DBRD appears to initially have been built around the idea notifying an application of a hardware failure, and the application taking appropriate steps to move access to a new primary. This is not a useful pattern for our case.

DRBD 9 mentions a way based on quorums:

https://linbit.com/drbd-user-guide/drbd-guide-9_0-en/#s-configuring-quorum

if i understand correctly, loss of quorum (i.e. current node is in the minority partition) results in IO being frozen until quorum is reestablished. This is exciting news, as we have good experience with ceph recovering this way without intervention.

the DRBD manual sadly then mentions in section 12

https://linbit.com/drbd-user-guide/drbd-guide-9_0-en/#ch-ocfs2

All cluster file systems require fencing – not only through the DRBD resource, but STONITH! A faulty member must be killed.

which is the opposite of what it says earlier in quorum docs.

i'm not sure why it would require fencing anyway if quorum is supposed to already prevent the minority partition from executing write I/O. Is this because quorum does not actually work with dual-primary?

已采纳解答

原帖链接 · Dok · CC BY-SA 4.0

Dual primary is limited to only two nodes. See this warning in the DRBD user's guide.

In DRBD 9.0.x Dual-Primary mode is limited to exactly 2 Primaries for the use in live migration.

Quorum requires 3 nodes or more. Thus you cannot use quorum in conjunction with dual-primary mode.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2023-03-12)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。