On 10/05/2017 11:03, Roman Mamedov wrote:
First thing that comes to mind, you should look into setting the remote device as --write-mostly, so that the local one is preferred for all reads (as long as it's up).
Sure, and it is planned. However, for initial testing, I want to leave as many parameters to their default settings.
But to be honest DRBD may indeed be a better solution for this use case, as it's built specifically with it in mind, and likely has all the various gotchas that might arise already thought about and handled properly.
To tell the truth, I already use DRBD 8.4 in production workloads and I are quite satisfied with it. However, DRBD 8.4 only supports 2 hosts (ie: master and slave), and DRBD 9.x (which supports multi-node replication) is a relatively new, deep re-write of the old codebase which significantly expanded scope.
So my interest in mdadm-based network replication... -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti@xxxxxxxxxx - info@xxxxxxxxxx GPG public key ID: FF5F32A8 -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
