Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-14566

Skip discovery in LNetPrimaryNID when lnet_peer_discovery_disabled is set

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • Lustre 2.15.0
    • None
    • None
    • 9223372036854775807

    Description

      If discovery is disabled locally then the discovery thread will not
      modify any peer objects as a result of the discovery process. Thus,
      the primary NID of any peer we're asked to discover will not change
      as a result of discovery. Therefore, we do not need to actually
      perform discovery in LNetPrimaryNID() if discovery is disabled
      locally. Since this routine can result in long client mount times
      when a Lustre server is down we should avoid this unnecessary
      discovery.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. LU-14668 LNet: do discovery in the background

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              hornc Chris Horn
              hornc Chris Horn
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: