Skip to content
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

Issue 6328 - vlv control may not be logged #6354

Merged
merged 1 commit into from
Oct 4, 2024
Merged

Conversation

progier389
Copy link
Contributor

@progier389 progier389 commented Oct 3, 2024

VLV control is logged only after succesfully sending the VLV response control
which means that VLV is not visible if the search fail which make troubleshooting harder.
This fix, logs the VLV (with None as vlv result) everytime a VLV is used

This fix also improve lmdb debug log about VLVs

Issue: #6328

Reviewed by: @tbordaz, @droideck (Thanks!)

Copy link
Member

@droideck droideck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code looks good to me!

However, I'm slightly concerned about potential performance impact...
Maybe we could add an on/off switch for detailed VLV logging?

But if you've already checked and it's not really slowing things down, then nevermind!

Copy link
Contributor

@tbordaz tbordaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@progier389
Copy link
Contributor Author

About the performance concern:
This fix only impacts the failing VLV searches which means that in practice in a working production server it seldom triggers. Getting performance issue would mean an heavy load of failing VLV searches and probably that something is seriously broken. And IMHO in this case it is better to be aware that the failing search are VLV one ...

@progier389 progier389 merged commit b808a2d into 389ds:main Oct 4, 2024
197 checks passed
progier389 added a commit that referenced this pull request Oct 18, 2024
VLV control is logged only after succesfully sending the VLV response control
which means that VLV is not visible if the search fail which make troubleshooting harder.
This fix, logs the VLV (with None as vlv result) everytime a VLV is used

This fix also improve lmdb debug log about VLVs

Issue: #6328

Reviewed by: @tbordaz, @droideck (Thanks!)

(cherry picked from commit b808a2d)
progier389 added a commit that referenced this pull request Oct 18, 2024
VLV control is logged only after succesfully sending the VLV response control
which means that VLV is not visible if the search fail which make troubleshooting harder.
This fix, logs the VLV (with None as vlv result) everytime a VLV is used

This fix also improve lmdb debug log about VLVs

Issue: #6328

Reviewed by: @tbordaz, @droideck (Thanks!)

(cherry picked from commit b808a2d)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants