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

add ability for named Changelog consumers

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • Lustre 2.12.8, Lustre 2.15.0
    • None
    • None
    • 9223372036854775807

    Description

      Currently Lustre Changelog consumers are always named e.g. "cl1" or "cl14". It would be useful to be able to declare the changelog username (e.g. "cl-rbh" or "cl-audit") so that it is clear who the Changelog users are, and to avoid duplicate changelog registrations. Otherwise, it can happen that the original Changelog user registration can be lost, and the application registers a new user, and the old user causes the Changelog records to accumulate.

      Attachments

        Issue Links

          Activity

            [LU-13055] add ability for named Changelog consumers
            adilger Andreas Dilger made changes -
            Link New: This issue is related to ATEMPO-17 [ ATEMPO-17 ]

            "Andreas Dilger <adilger@whamcloud.com>" merged in patch https://review.whamcloud.com/c/doc/manual/+/57435/
            Subject: LU-13055 doc: add changelog_register name/mask
            Project: doc/manual
            Branch: master
            Current Patch Set:
            Commit: 49a66627ea6fd91d0fe475a031b5ba9fa8e6f7bd

            gerrit Gerrit Updater added a comment - "Andreas Dilger <adilger@whamcloud.com>" merged in patch https://review.whamcloud.com/c/doc/manual/+/57435/ Subject: LU-13055 doc: add changelog_register name/mask Project: doc/manual Branch: master Current Patch Set: Commit: 49a66627ea6fd91d0fe475a031b5ba9fa8e6f7bd

            "Andreas Dilger <adilger@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/doc/manual/+/57435
            Subject: LU-13055 doc: add changelog_register name/mask
            Project: doc/manual
            Branch: master
            Current Patch Set: 1
            Commit: a19e58c24a1a194358b242eab35e00534556aa07

            gerrit Gerrit Updater added a comment - "Andreas Dilger <adilger@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/doc/manual/+/57435 Subject: LU-13055 doc: add changelog_register name/mask Project: doc/manual Branch: master Current Patch Set: 1 Commit: a19e58c24a1a194358b242eab35e00534556aa07
            adilger Andreas Dilger made changes -
            Link New: This issue is related to DOE-70 [ DOE-70 ]
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-14699 [ LU-14699 ]
            tappro Mikhail Pershin made changes -
            Link New: This issue is related to LU-16268 [ LU-16268 ]
            pjones Peter Jones made changes -
            Link New: This issue is duplicated by LU-13338 [ LU-13338 ]

            For context, llapi_changelog_start() works by opening /dev/changelog-MDTnnnn and then llapi_changelog_recv() reads from the file descriptor. There is no obvious way to make the kernel side aware of which changelog user is reading the log, so some new mechanism would have to be added.

            olaf Olaf Weber (Inactive) added a comment - For context, llapi_changelog_start() works by opening /dev/changelog-MDT nnnn and then llapi_changelog_recv() reads from the file descriptor. There is no obvious way to make the kernel side aware of which changelog user is reading the log, so some new mechanism would have to be added.

            Andreas, right, mask is used to decide what record to write. As for processing case, if we know particular user doing that processing then I think it is possible to filter records

            tappro Mikhail Pershin added a comment - Andreas, right, mask is used to decide what record to write. As for processing case, if we know particular user doing that processing then I think it is possible to filter records
            adilger Andreas Dilger made changes -
            Link New: This issue is related to EX-2102 [ EX-2102 ]

            People

              tappro Mikhail Pershin
              adilger Andreas Dilger
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: