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

client grab open lock after N opens

    XMLWordPrintable

Details

    • Improvement
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • Lustre 2.9.0
    • None
    • None
    • cent server/sles client
    • 9223372036854775807

    Description

      listed as minor but when a user does this, we start to get phone calls form other users and then page POC to identify code/user. Workaround is to terminate user job(s).

      Oleg has said that Lustre has an existing feature for a client to acquire open lock but off by default. This to mimic NFS behavior.

      Ideal change would be that we can specify a number of times that a file is opened on single client at which time lock is acquired. (e.g. 10th time)

      Use case is naive user who loop in this way on like 5000+ threads in java:

      do until till the sun turns black()

      { fd = open(*my_thread_ID, O_APPEND) calculate_something_small_but_useful() write(fd, *fortytwo, 42) close(fd }

      Users often don't have complete control over the code they run and as a result may not be able to quickly make even simple changes.

      Attachments

        Issue Links

          Activity

            People

              green Oleg Drokin
              Bob.C Bob Ciotti
              Votes:
              0 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated: