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/LU-11050 Lustre <p>From what I could read in mdd_object.c the procfile changelog_deniednext is the number of seconds to wait before logging another NOPEN changelog record.</p> <p>The implementation computes a deadline once (when an NOPEN is logged) instead of comparing the current time + the timeout. This means that if somebody sets the timeout to 3600s, produces an NOPEN changelog and then sets back the timeout to 60s, one will still need to wait an hour to see the next NOPEN changelog.</p> LU-11050

mdd: modifying changelog_deniednext does not yield immediate result

Bug Minor Open Unresolved Sebastien Buisson CEA Wed, 23 May 2018 12:44:44 +0000 Wed, 5 Aug 2020 13:50:22 +0000 0 4 <p>Quentin</p> <p>Is this something that you are planning to work on?</p> <p>Peter</p> <p>I was hoping someone else could do it...</p> <p>Sebastien</p> <p>Could you please comment?</p> <p>Thanks</p> <p>Peter</p> <p>Hi,</p> <p>What you describe is how the changelog_deniednext tunable was designed. As the name tends to suggest, it defines when the next NOPEN Changelog entry will be recorded, counting from the last recorded entry.<br/> This implementation was suggested by Andreas. It is slightly more efficient to add changelog_deniednext delay when saving denied time, and then just compare against that, instead of adding changelog_deniednext delay to denied time for each check.</p> <p>Thanks,<br/> Sebastien.</p> <p>How about re-computing the deadline everytime the proc file is written to?</p> Related LU-9727 Development Rank 1|hzzxo7: Rank (Obsolete) 9223372036854775807 Severity