-
Notifications
You must be signed in to change notification settings - Fork 395
expire: New MAIN.n_superseded counter #4045
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the bikeshed, I really think superseded is better: If my understanding of the English language is adequate, it makes clear that a specific object is replaced by something which makes the previous object redundant.
Replaced is too general, in my mind: Cache objects can be LRU-replaced by whatever
include/tbl/vsl_tags.h
Outdated
@@ -360,6 +360,8 @@ SLTM(ExpKill, 0, "Object expiry event", | |||
"\tLogged when the expiry thread expires an object.\n\n" | |||
"EXP_Removed\n" | |||
"\tLogged when the expiry thread removes an object before expiry.\n\n" | |||
"VBF_Replace\n" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
VBF_Superseded
for consistency? (also mentioned by phk)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ack
👍 but I really think it should be superseded, not "replaced". |
Bugwash: OK. I will apply @nigoroll's suggestions and merge. |
Rebased against master, to be merged once CI passes. |
I ran into a case where a user was refining their cache policy and this turned out to be a blind spot.