Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: Lustre 2.0.0, Lustre 1.8.6
    • Fix Version/s: Lustre 2.2.0
    • Labels:
      None
    • Bugzilla ID:
      18,767
    • Rank (Obsolete):
      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

        1. Imperative Recovery Design Document.pdf
          428 kB
          Jinshan Xiong
        2. Imperative Recovery Scope Statement.pdf
          109 kB
          Jinshan Xiong
        3. Imperative Recovery Test Plan Rev A.pdf
          217 kB
          Jinshan Xiong
        4. LUG11_Imperative_Recovery.pdf
          399 kB
          Jinshan Xiong

          Issue Links

            Activity

              People

              • Assignee:
                jay Jinshan Xiong (Inactive)
                Reporter:
                jay Jinshan Xiong (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: