• Type: Technical task
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Rank (Obsolete):


      Readwrite Persistent Client Cache has been implemented by using HSM features (LU-10092). When a file is cached on Readwrite PCC (RW-PCC), only this single client can read/write to the file. RW-PCC can accelerate I/O intensive applications which read/write data into a file in a single client. However, in some other use cases, part of the files will never be updated, but need to be readed at the same time from multiple clients. Readonly Persistent Client Cache tries to implement a readonly cache level on Lustre clients using SSDs/NVMe.

      Readonly Persistent Client Cache (RO-PCC) shares the same framework with Readwrite Persistent Client Cache, except that no HSM mechanism is used in readonly mode of PCC. Instead, readonly mode of PCC uses grouplock to protect the data from being written from other clients.

      Whenever a file is fetched into RO-PCC, like the archive number of RW-PCC, a grouplock ID needs to be specified. The grouplock of this ID will be held in the client as long as the file is being cached in RO-PCC. Multiple clients can fetch the same file into its local cache using the same grouplock ID. Because of the semantics of grouplock, no other client can read/write from/to the file if the grouplock with the same ID is not held. Also because of the semantics of grouplock, no client can fetch the file to RO-PCC with a different grouplock ID.


          Issue Links



              • Assignee:
                qian_wc Qian Yingjin
                lixi Li Xi (Inactive)
              • Votes:
                0 Vote for this issue
                11 Start watching this issue


                • Created: