https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-13934 Lustre <p>ldev.conf appears to specify a primary and single failover node (<a href="http://doc.lustre.org/lustre_manual.xhtml#dbdoclet.zfssnapshotConfig" class="external-link" target="_blank" rel="nofollow noopener">http://doc.lustre.org/lustre_manual.xhtml#dbdoclet.zfssnapshotConfig</a>).</p> <p> </p> <p>However, It's not necessarily the case that resources are limited to a primary and failover pair; there may be more placements than two.</p> <p> </p> <p>For example, Exascaler HA is configured such that an OST could be mounted on any of  four available VMs.</p> <p> </p> <p>It seems that we should expand the ldev.conf such that multiple failovers could be listed after the primary.</p> LU-13934

ldev.conf should consider multiple failover nodes

Bug Major Open Unresolved WC Triage Joe Grund lsnapshot Thu, 27 Aug 2020 14:14:25 +0000 Wed, 30 Sep 2020 15:10:32 +0000 0 4 <p>Concern here is what happens to snapshot commands if one of the lustre targets cannot be found due to it being mounted on a different node than what's listed in primary / failover. This appears possible for everything besides the MGS which is currently constrained to two VMS.</p> Related Development Rank 1|i018hz: Rank (Obsolete) 9223372036854775807 Severity