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.

Sign up for GitHub

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

Jump to bottom

Improve DB Locks Monitoring Feature Descriptions #4803

Closed
droideck opened this issue Jun 11, 2021 · 3 comments · Fixed by #4810
Closed

Improve DB Locks Monitoring Feature Descriptions #4803

droideck opened this issue Jun 11, 2021 · 3 comments · Fixed by #4810
Labels
documentation Improvements or additions to documentation
Milestone
1.4.3

Comments

@droideck
Copy link
Member

Issue Description
The description of the field "nsslapd-db-locks-monitoring-threshold" is unclear.

"Sets the DB lock exhaustion value in percentage (valid range is 70-95). 
If too many locks are acquired, the server will abort the searches while the number of locks are not decreased.
It helps to avoid DB corruption and long recovery. ()"

Package Version and Platform:

  • Package and version: 389-ds-base, master

Additional context
Probably, we can improve it like this:

"When the threshold is reached, all searches are aborted until the number of active locks decreases below the configured threshold."

Also, we should mention that the RHDS admin is expected to do something here.

Other parts of the feature docs can be improved.
@droideck droideck added the needs triage The issue will be triaged during scrum label Jun 11, 2021
@droideck
Copy link
Member Author

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1970971

@droideck droideck mentioned this issue Jun 17, 2021
Merged
@droideck droideck added the documentation Improvements or additions to documentation label Jun 23, 2021
@droideck droideck added this to the 1.4.3 milestone Jun 23, 2021
@droideck droideck removed the needs triage The issue will be triaged during scrum label Jun 23, 2021
@droideck droideck mentioned this issue Jun 23, 2021
Closed
droideck added a commit that referenced this issue Jun 23, 2021
@droideck
Issue 4803 - Improve DB Locks Monitoring Feature Descriptions (#4810)
72964fe 
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 issue Jun 23, 2021
@droideck
Issue 4803 - Improve DB Locks Monitoring Feature Descriptions (#4810)
e7b781b 
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 issue Jun 23, 2021
@droideck
Issue 4803 - Improve DB Locks Monitoring Feature Descriptions (#4810)
724763b 
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
Copy link
Member Author

eb90e23..e7b781b 389-ds-base-1.4.3 -> 389-ds-base-1.4.3
8de81d5..724763b 389-ds-base-1.4.4 -> 389-ds-base-1.4.4

droideck added a commit that referenced this issue Jun 23, 2021
@droideck
Issue 4803 - Improve DB Locks Monitoring Feature Descriptions
9ee03bc 
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 issue Jun 23, 2021
@droideck
Issue 4803 - Improve DB Locks Monitoring Feature Descriptions
a82ac96 
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 issue Jun 23, 2021
@droideck
Issue 4803 - Improve DB Locks Monitoring Feature Descriptions
5c88c00 
Description: Enchance one line for the threshold setting
as per comment in #4810

Relates: #4803

Reviewed by: @droideck (one line rule)
@droideck
Copy link
Member Author

Improve the description as per the comment - #4810 (review)
72964fe..9ee03bc master -> master
e7b781b..a82ac96 389-ds-base-1.4.3 -> 389-ds-base-1.4.3
724763b..5c88c00 389-ds-base-1.4.4 -> 389-ds-base-1.4.4

lab-at-nohl pushed a commit to lab-at-nohl/cockpit-389-ds-containerproxy that referenced this issue May 9, 2024
@droideck
Issue 4803 - Improve DB Locks Monitoring Feature Descriptions (#4810)
f822c93 
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: 389ds/389-ds-base#4803

Reviewed by: @tbordaz (Thank you!)
lab-at-nohl pushed a commit to lab-at-nohl/cockpit-389-ds-containerproxy that referenced this issue May 9, 2024
@droideck
Issue 4803 - Improve DB Locks Monitoring Feature Descriptions
9f5f6a1 
Description: Enchance one line for the threshold setting
as per comment in 389ds/389-ds-base#4810

Relates: 389ds/389-ds-base#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
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
1.4.3
Development

Successfully merging a pull request may close this issue.

Issue 4803 - Improve DB Locks Monitoring Feature Descriptions
1 participant
@droideck