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 4803 - Improve DB Locks Monitoring Feature Descriptions #4810

Merged
merged 2 commits into from Jun 23, 2021
Merged

Issue 4803 - Improve DB Locks Monitoring Feature Descriptions #4810

merged 2 commits into from Jun 23, 2021

Conversation

droideck
Copy link
Member

Description: The description of the field "nsslapd-db-locks-monitoring-threshold"
is unclear. Make the explanations more detailed and concise in both CLI
and Web UI.

Fixes: #4803

Reviewed by: ?

Description: The description of the field "nsslapd-db-locks-monitoring-threshold"
is unclear. Make the explanations more detailed and concise in both CLI
and Web UI.

Fixes: #4803

Reviewed by: ?
@tbordaz
Copy link
Contributor

tbordaz commented Jun 21, 2021

Descriptions are looking good to me. Should they also mention the default value ?
ACK

@droideck droideck added this to the 1.4.3 milestone Jun 23, 2021
@droideck droideck added the documentation Improvements or additions to documentation label Jun 23, 2021
@droideck droideck merged commit 72964fe into 389ds:master Jun 23, 2021
Copy link

@EmmanuelKasper EmmanuelKasper left a comment

Choose a reason for hiding this comment

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

Thanks Simon, very clear explanation, I am just concerned about the sentence:
It helps to avoid DB corruption and long recovery.
It is either saying too little or too much.

I would here rather write:
This threshold is a safeguard against DB corruption which might be caused by locks exhaustion.

or get rid of it, if the field description is too long.

droideck added a commit that referenced this pull request Jun 23, 2021
Description: The description of the field "nsslapd-db-locks-monitoring-threshold"
is unclear. Make the explanations more detailed and concise in both CLI
and Web UI.

Fixes: #4803

Reviewed by: @tbordaz (Thank you!)
droideck added a commit that referenced this pull request Jun 23, 2021
Description: The description of the field "nsslapd-db-locks-monitoring-threshold"
is unclear. Make the explanations more detailed and concise in both CLI
and Web UI.

Fixes: #4803

Reviewed by: @tbordaz (Thank you!)
@droideck droideck removed this from the 1.4.3 milestone Jun 23, 2021
droideck added a commit that referenced this pull request Jun 23, 2021
Description: Enchance one line for the threshold setting
as per comment in #4810

Relates: #4803

Reviewed by: @droideck (one line rule)
droideck added a commit that referenced this pull request Jun 23, 2021
Description: Enchance one line for the threshold setting
as per comment in #4810

Relates: #4803

Reviewed by: @droideck (one line rule)
droideck added a commit that referenced this pull request Jun 23, 2021
Description: Enchance one line for the threshold setting
as per comment in #4810

Relates: #4803

Reviewed by: @droideck (one line rule)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improve DB Locks Monitoring Feature Descriptions
3 participants