[LU-11050] mdd: modifying changelog_deniednext does not yield immediate result

• Status: Open
• Project: Lustre
• Type: Bug
• Priority: Minor
• Reporter: CEA
• Assignee: Sebastien Buisson
• Resolution: Unresolved
• Severity: 3

Description

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.

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.

Issue Links

• is related to: LU-9727 Lustre Audit with Changelogs

Comments

[Peter Jones]

Quentin

Is this something that you are planning to work on?

Peter

[Quentin Bouget]

I was hoping someone else could do it...

[Peter Jones]

Sebastien

Could you please comment?

Thanks

Peter

[Sebastien Buisson (Inactive)]

Hi,

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.
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.

Thanks,
Sebastien.

[Quentin Bouget]

How about re-computing the deadline everytime the proc file is written to?