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-2605 Lustre <p>In case of failure of the 1st server, the MDS1 and the OSS1 will fail in the same time.</p> <p>Then the failover on the 2nd node will wait 5 more minutes because the moved OST will wait the timeout for the failed client MDS1.</p> <p>This case of 2 servers with failover and 2 active OSS is important for little configurations.</p> <p>(BULL)</p> Linux, 2 physical servers,<br/> the 1st holds the active MDS and an active OSS and the 2nd holds the passive MDS and an active OSS LU-2605

reduce the failover time when the MDS and OSS are on the same machine in High Availability

Improvement Trivial Resolved Duplicate WC Triage gmsw server Fri, 11 Jan 2013 06:00:26 +0000 Thu, 11 Jun 2020 09:51:33 +0000 Thu, 11 Jun 2020 09:51:33 +0000 Lustre 2.1.0 0 3 <p>This is somewhat expected behaviour if the MDT and OST are on the same node, which is why we do not recommend this configuration. However, the MDT connection to the OST1 (regardless of which node it is running on) should always use the same connection UUID even after a reboot (unlike a client node, which is always gets a new UUID for each mount), and so the failed-over MDT should be able to participate in recovery on node 2 as well.</p> <p>Do you mount the MDT on node 2 at the same time as OST1?</p> <p>Do you also have a lustre client mounted locally on the MDS/OSS server node? This would be more likely to be the cause of this recovery slowdown. Does this slow recovery also happen if you restart the MDT and OST on node 1 again, instead of failing over to node 2?</p> <p>Having your actual console logs from during the recovery would make this more clear.</p> <p>This ticket is actually related to a question i got during a training class (i.e. is it safe to run the MDT on the same node as OSTs?).<br/> I replied that the only problem (Andreas, can you think of anything else?) i could think of is this recovery issue since the MDS might not be able to join recovery. That said, Andreas is right, we reuse the same UUID and allow the MDS to reconnect. As a result, OSTs should be able to complete recovery.</p> <p>This should be fixed with patch <a href="https://review.whamcloud.com/36025" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/36025</a> "<tt><a href="https://jira.whamcloud.com/browse/LU-12722" title="exclude local client mounted on MDS/OSS from recovery" class="issue-link" data-issue-key="LU-12722"><del>LU-12722</del></a> target: disable recovery for local clients</tt>"</p> Related LU-12722 Development Rank 1|hzvezr: Rank (Obsolete) 6074