https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LUDOC-366 Lustre Documentation <p>NRS Delay is a new feature slated for Lustre 2.10. It probably does not need extensive documentation because it is intended for use in development and testing, however we should probably at least document how it can be configured via the lctl command.</p> <p>The commit comment for the patch contains a number of examples. Patch is here <a href="https://review.whamcloud.com/#/c/14701" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/#/c/14701</a></p> <p>The development ticket is <a href="https://jira.whamcloud.com/browse/LU-6283" title="NRS Delay Policy" class="issue-link" data-issue-key="LU-6283"><del>LU-6283</del></a></p> LUDOC-366

Document NRS Delay

New Feature Minor Resolved Fixed Chris Horn Chris Horn Tue, 7 Mar 2017 23:48:33 +0000 Wed, 29 May 2019 17:36:47 +0000 Wed, 25 Oct 2017 15:42:13 +0000 0 4 <p>Chris</p> <p>Could you please provide a patch to cover the explanation of how this feature works for the manual? If it is problematic for you to work out the syntax for the formatting then please just attach a text file and we can find someone to help with the formatting aspect</p> <p>Thanks</p> <p>Peter</p> <p>Yes, I'll provide a patch</p> <p>Chris Horn (hornc@cray.com) uploaded a new patch: <a href="https://review.whamcloud.com/27501" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/27501</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LUDOC-366" title="Document NRS Delay" class="issue-link" data-issue-key="LUDOC-366"><del>LUDOC-366</del></a> nrs: Add delay policy document<br/> Project: doc/manual<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 05202973255b4f2d4a75238012bf2730d54a82e5</p> <p>Andreas Dilger (andreas.dilger@intel.com) merged in patch <a href="https://review.whamcloud.com/27501/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/27501/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LUDOC-366" title="Document NRS Delay" class="issue-link" data-issue-key="LUDOC-366"><del>LUDOC-366</del></a> nrs: Add delay policy document<br/> Project: doc/manual<br/> Branch: master<br/> Current Patch Set: <br/> Commit: be36f62196439346aada3008072120a54d59e4a3</p> <p>Hi,</p> <p>Can we get some attention here? This has been lingering for quite a while and appears ready to land..</p> <p>Wrong ticket?</p> <p>I'm looking at the last activity here, it's been stale since '17 and this work was long ago completed.</p> <p>Could you please be more specific? The above change looks like it landed a couple of years ago. The ticket is marked as RESOLVED. What else are you expecting to happen.</p> <p>This is in regards to resolved vs closed. so you can ignore. I now understand that for you guys, resolved is a closed state that you all utilize. We generally mark bugs "closed" once they land as "resolved" would mean, work is complete, landing is happening and once landed it will be transitioned into closed. We utilize labels to keep track of which branches it's landing into and which branches are requested for it.</p> <p> </p> <p>Cheers.</p> Related LU-6283 Development Rank 1|hzz67r: Rank (Obsolete) 9223372036854775807