[Drbd-dev] drbd: a proposal of two-primaries mode

[rui.xu]

Hi Joel,


For the first question, we have another component in our system implements paxos and provide distribute lock.

When  the network connection between two nodes is disconnected, the first node that can get the distributed lock
will continue to provide services, so we can handle this case.


For the second question, we have to use iSCSI in my case.



For the last question, we have implemented our own cluster manager, the first version for failover is same with what you suggested.

But in my use-case, it introduce much IO-non-response time in failover. So we want to provide two active iscsi pathes for client then

the client can do failover by his multipath software. 



Best regards,
Xu





From: Joel Colledge <joel.colledge at linbit.com>
Date: 2022-05-10 20:55:15
To:  "rui.xu" <rui.xu at easystack.cn>
Cc:  Philipp Reisner <philipp.reisner at linbit.com>,drbd-dev at lists.linbit.com,dongsheng.yang at easystack.cn
Subject: Re: Re: drbd: a proposal of two-primaries mode>Hi Xu,
>
>Dual primary mode is not recommended for this scenario due to data
>divergence considerations. How do you handle a loss of network
>connectivity between the storage nodes?
>
>Is it possible to use diskless DRBD clients instead of iSCSI
>initiators for your purposes?
>
>Assuming you have to use iSCSI, the normal solution is to only have
>one active target. Use a cluster manager to support failover to the
>other storage node. For instance, add a third node with minimal
>resources as a diskless tiebreaker, enable DRBD quorum, and use the
>drbd-reactor promoter as a simple cluster manager. Have you considered
>this option?
>
>Best regards,
>Joel




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-dev/attachments/20220511/0edee697/attachment.htm>