[LU-19] imperative recovery

• Type: New Feature
• Resolution: Fixed
• Priority: Blocker
• Fix Version/s: Lustre 2.2.0
• Affects Version/s: Lustre 2.0.0, Lustre 1.8.6
• Bugzilla ID: 18,767
• Assignee: Jinshan Xiong (Inactive)
• Reporter: Jinshan Xiong (Inactive)

Description

Imperative recovery means the clients are notified explicitly when and where a failed target has
restarted. Ideally the notification should occur after the target has mounted and is waiting for
connections. A fully automated version of this will require a new mechanism for distributing node
health information efficiently. A simple, initial version can be done as a /proc file for each
import that can be used to initiate recovery.

Issue Links

• is related to: LU-573 conf-sanity test_22: @@@@@@ FAIL: test_22 failed with 41
• is related to: LU-10360 use Imperative Recovery logs for client->MDT/OST connections
• is related to: LU-13306 allow clients to accept mgs_nidtbl_entry with IPv6 NIDs
• is related to: LU-569 make lu_object cache size adjustable