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

LNet: lnd_timeout value reported by lnetctl may be different from what is actually used

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.16.0
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      There's an lnd_timeout calculated as a function of transaction_timeout and retry_count. This is the value displayed by "lnetctl global show". However, each LND may define its own timeout by setting timeout module parameter to a positive value, which overrides the higher-level lnd_timeout defined by LNet.

      It is misleading to report only LNet-level timeout. __ Since actual timeout is lnd-specific, it should be reported among the settings per corresponding LND.

      Attachments

        Activity

          People

            fsehr Frank Sehr
            ssmirnov Serguei Smirnov
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: