Details

    • Improvement
    • Resolution: Fixed
    • Critical
    • Lustre 2.6.0
    • Lustre 2.6.0
    • None
    • 12532

    Description

      OBJECT_UPDATE_PER_RPC_MAX is a internal to OUT's implementation limit. OUT can use RPC directly instead of copying arguments into env. OUT just needs to maintain resizable array of object pointers.
      probably in the same patch we could introduce a way to negotiate max.update buffer between the peers.

      Attachments

        Issue Links

          Activity

            [LU-4585] remove OBJECT_UPDATE_PER_RPC_MAX

            Patch landed to Master. Please reopen if more work is needed.

            jlevi Jodi Levi (Inactive) added a comment - Patch landed to Master. Please reopen if more work is needed.
            di.wang Di Wang added a comment - http://review.whamcloud.com/9804
            di.wang Di Wang added a comment -

            reopen the ticket, since this will cause the memory leak.

            di.wang Di Wang added a comment - reopen the ticket, since this will cause the memory leak.

            Patch landed to Master. Please reopen ticket if more work is needed.

            jlevi Jodi Levi (Inactive) added a comment - Patch landed to Master. Please reopen ticket if more work is needed.
            di.wang Di Wang added a comment - http://review.whamcloud.com/9590

            This should be fixed in 2.6 so that we don't get into problems with the protocol in later versions.

            adilger Andreas Dilger added a comment - This should be fixed in 2.6 so that we don't get into problems with the protocol in later versions.

            People

              di.wang Di Wang
              bzzz Alex Zhuravlev
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: