Details
-
New Feature
-
Resolution: Fixed
-
Blocker
-
Lustre 2.0.0, Lustre 1.8.6
-
None
-
18,767
-
10457
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.
Attachments
Issue Links
- is related to
-
LU-573 conf-sanity test_22: @@@@@@ FAIL: test_22 failed with 41
-
- Resolved
-
-
LU-10360 use Imperative Recovery logs for client->MDT/OST connections
-
- Open
-
-
LU-13306 allow clients to accept mgs_nidtbl_entry with IPv6 NIDs
-
- Resolved
-
- is related to
-
LU-569 make lu_object cache size adjustable
-
- Closed
-
Activity
Link | New: This issue is related to LU-18525 [ LU-18525 ] |
Link | New: This issue is related to LU-13752 [ LU-13752 ] |
Link | New: This issue is related to AEON-46 [ AEON-46 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Fix Version/s | New: Lustre 2.2.0 [ 10082 ] | |
Issue Type | Original: Improvement [ 4 ] | New: New Feature [ 2 ] |
Attachment | New: Imperative Recovery Scope Statement.pdf [ 10766 ] | |
Attachment | New: Imperative Recovery Design Document.pdf [ 10767 ] | |
Attachment | New: Imperative Recovery Test Plan Rev A.pdf [ 10768 ] | |
Attachment | New: LUG11_Imperative_Recovery.pdf [ 10769 ] |
Link | New: This issue is duplicated by ORNL-8 [ ORNL-8 ] |
Link | New: This issue is related to ORNL-14 [ ORNL-14 ] |