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

disabling the xattr cache on client for LSOM

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • Lustre 2.16.0, Lustre 2.15.3
    • None
    • None
    • 9223372036854775807

    Description

      Currently, to get uptodate LSOM data, we need to set llite.*.xattr_cache=0 to disable the xattr cache on client completely. This may lead that other kind of xattr can not be cached on client too.

      This ticket mainly focues on the heavy-weight solution to disable caching only for LSOM xattr data ("trusted.som") on client.

      Attachments

        Issue Links

          Activity

            [LU-11695] disabling the xattr cache on client for LSOM

            "Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/49952/
            Subject: LU-11695 som: disabling xattr cache for LSOM on client
            Project: fs/lustre-release
            Branch: b2_15
            Current Patch Set:
            Commit: dcd842e870a099e18a9afcb817f382648c96bed0

            gerrit Gerrit Updater added a comment - "Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/49952/ Subject: LU-11695 som: disabling xattr cache for LSOM on client Project: fs/lustre-release Branch: b2_15 Current Patch Set: Commit: dcd842e870a099e18a9afcb817f382648c96bed0

            "Jian Yu <yujian@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/49952
            Subject: LU-11695 som: disabling xattr cache for LSOM on client
            Project: fs/lustre-release
            Branch: b2_15
            Current Patch Set: 1
            Commit: e32b3e958a1210c8b082668a7afc936c3e5f16fe

            gerrit Gerrit Updater added a comment - "Jian Yu <yujian@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/49952 Subject: LU-11695 som: disabling xattr cache for LSOM on client Project: fs/lustre-release Branch: b2_15 Current Patch Set: 1 Commit: e32b3e958a1210c8b082668a7afc936c3e5f16fe
            pjones Peter Jones added a comment -

            Landed for 2.16

            pjones Peter Jones added a comment - Landed for 2.16

            "Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/33711/
            Subject: LU-11695 som: disabling xattr cache for LSOM on client
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: 192902851d73ec246af92a2ff7be8f23b08c4343

            gerrit Gerrit Updater added a comment - "Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/33711/ Subject: LU-11695 som: disabling xattr cache for LSOM on client Project: fs/lustre-release Branch: master Current Patch Set: Commit: 192902851d73ec246af92a2ff7be8f23b08c4343

            It turns out that the trusted.som xattr is not used directly on the client for anything except "lfs getsom", so keeping it in the xattr cache doesn't help any real workload, and only serves to confuse tests that are using getsom and see a cached value that is stale.

            I've un-abandoned patch https://review.whamcloud.com/33711 "LU-11695 som: disabling xattr cache for LSOM on client", but it will need to be rebased to resolve conflicts.

            adilger Andreas Dilger added a comment - It turns out that the trusted.som xattr is not used directly on the client for anything except " lfs getsom ", so keeping it in the xattr cache doesn't help any real workload, and only serves to confuse tests that are using getsom and see a cached value that is stale. I've un-abandoned patch https://review.whamcloud.com/33711 " LU-11695 som: disabling xattr cache for LSOM on client ", but it will need to be rebased to resolve conflicts.

            Now that the statx() patch is landing, I think this patch should be abandoned, and this ticket closed.

            adilger Andreas Dilger added a comment - Now that the statx() patch is landing, I think this patch should be abandoned, and this ticket closed.
            lixi_wc Li Xi added a comment -

            I think at least currently, there is no requirement to use the client side interface to acess the LSOM. So, I'd suggest to delay the implement of this API until we started to see some real requirement for it. After all, LSOM is designed for MDT scanning, not client side accessment. And I think Yingjin's patch is enough to fix the test problem for now.

            lixi_wc Li Xi added a comment - I think at least currently, there is no requirement to use the client side interface to acess the LSOM. So, I'd suggest to delay the implement of this API until we started to see some real requirement for it. After all, LSOM is designed for MDT scanning, not client side accessment. And I think Yingjin's patch is enough to fix the test problem for now.

            People

              qian_wc Qian Yingjin
              qian_wc Qian Yingjin
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: