Details

    • Technical task
    • Resolution: Fixed
    • Minor
    • Lustre 2.8.0
    • None
    • None
    • 8086

    Attachments

      Issue Links

        Activity

          [LU-3266] Regression tests for NRS policies
          pjones Peter Jones added a comment -

          Landed for 2.8

          pjones Peter Jones added a comment - Landed for 2.8

          Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/9286/
          Subject: LU-3266 test: regression tests for nrs policies
          Project: fs/lustre-release
          Branch: master
          Current Patch Set:
          Commit: 38b68e47e5e240fd8d394a944737ecdbcf2fb70f

          gerrit Gerrit Updater added a comment - Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/9286/ Subject: LU-3266 test: regression tests for nrs policies Project: fs/lustre-release Branch: master Current Patch Set: Commit: 38b68e47e5e240fd8d394a944737ecdbcf2fb70f

          Hi,

          I've added patch http://review.whamcloud.com/#/c/9286/.
          Think will be a lot of comments...

          scherementsev Sergey Cheremencev added a comment - Hi, I've added patch http://review.whamcloud.com/#/c/9286/ . Think will be a lot of comments...

          Sergey <sergey_cheremencev@xyratex.com> from our team has started working on addressing this ticket.

          nangelinas Nikitas Angelinas added a comment - Sergey <sergey_cheremencev@xyratex.com> from our team has started working on addressing this ticket.

          Hi,

          Andreas, apologies for the long delay, but I have been on a long (hopefully temporary) 'break' from Lustre work during the last few months. I have spoken to our core Lustre team to see who will be handling this, and hopefully other NRS maintenance work, and we will update with this information as soon as we decide on a way forward; I hope that is an acceptable solution, please let me know if not.

          nangelinas Nikitas Angelinas added a comment - Hi, Andreas, apologies for the long delay, but I have been on a long (hopefully temporary) 'break' from Lustre work during the last few months. I have spoken to our core Lustre team to see who will be handling this, and hopefully other NRS maintenance work, and we will update with this information as soon as we decide on a way forward; I hope that is an acceptable solution, please let me know if not.

          Nikitas,
          any progress on getting some regression tests for NRS? Just some basic tests to run each policy for a few minutes under load would be great.

          As it stands, I tried enabling NRS with the ORR policy on my home server (2.4.1) while it was under load and it crashed almost instantly (bug to be filed separately), so I don't think that code is getting enough testing.

          adilger Andreas Dilger added a comment - Nikitas, any progress on getting some regression tests for NRS? Just some basic tests to run each policy for a few minutes under load would be great. As it stands, I tried enabling NRS with the ORR policy on my home server (2.4.1) while it was under load and it crashed almost instantly (bug to be filed separately), so I don't think that code is getting enough testing.

          Instead of tracking the addition of NRS regression tests under LU-3239 (which is a bug and shouldn't be overloaded with this separate task), open this new ticket for the tests and their landing.

          There should be a test for each NRS policy type that enables the policy and does some reasonable number of operations using the policy. It shouldn't run for longer than about 5 minutes per policy (independent of the storage speed) so that it doesn't consume an inordinate amount of testing time for each patch. There needs to be both file-per-process and shared-single-file IO from multiple clients to exercise the different policies properly, so sanityn.sh is probably a good place for it.

          adilger Andreas Dilger added a comment - Instead of tracking the addition of NRS regression tests under LU-3239 (which is a bug and shouldn't be overloaded with this separate task), open this new ticket for the tests and their landing. There should be a test for each NRS policy type that enables the policy and does some reasonable number of operations using the policy. It shouldn't run for longer than about 5 minutes per policy (independent of the storage speed) so that it doesn't consume an inordinate amount of testing time for each patch. There needs to be both file-per-process and shared-single-file IO from multiple clients to exercise the different policies properly, so sanityn.sh is probably a good place for it.

          People

            wc-triage WC Triage
            jlevi Jodi Levi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: