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

ldlm: not expand the lock extent when the shared file is under lock contention

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • Minor
    • None
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      We already have the lock contention detection patch: https://review.whamcloud.com/35287/

      With lock contention detection, the lock server will mark the lock resource (a shared OST object) as contention in a time period (2 seconds, by default). And the client requested a extent lock will be informed the lock contention.

      Under lock contention, the lock server will not expand the lock extent to avoid unnecessary lock conflict callbacks.
      And the client could be switch from buffered I/O to the direct I/O if the I/O size is large enough.

      Attachments

        Issue Links

          Activity

            People

              qian_wc Qian Yingjin
              qian_wc Qian Yingjin
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: