#50960 [RFE] Advance options in RHDS Disk Monitoring Framework
Closed: wontfix 2 years ago by spichugi. Opened 2 years ago by spichugi.

Issue Description

Assuming the threshold is set for 50 MB, as soon the disk space is less than 50 MB, 389 DS will stop logging & when disk space is half the threshold i.e. 25MB ds will shut down, In this case, the application will come into the picture and in order to self heal, Try to start the ds, Since disk space is still an issue, 389 DS will again shut down the service & smanager will try to start it again. Well in this cycle, There is often chances data will get corrupt.
This RFE is opened to make rhds disk monitororing more robust.

Add two attributes to cn=config:

  • nsslapd-disk-monitoring-readonly-on-threshold - it accepts 'on/off' values and changes the original behavior so when we reach the threshold, we set the read-only mode (and then we do other actions - like disable non-critical logging, etc.). When we reach half of the threshold, we start the graceful shutdown as it was before. We don't start up if the disk space is still below half of the threshold.

  • nsslapd-disk-monitoring-shutdown-script - this attribute accepts a path to a script (any executable) which will be run at the moment of a graceful shutdown at half of the threshold (it will be run as the user who runs ns-slapd process). It will allow initiating the process which can take a backup, send mail to an admin about disk space alarm or any other custom command.

Metadata Update from @spichugi:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

2 years ago

Metadata Update from @spichugi:
- Issue assigned to spichugi

2 years ago

Metadata Update from @spichugi:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1728943

2 years ago

Metadata Update from @mreynolds:
- Issue priority set to: major
- Issue set to the milestone: 1.4.3

2 years ago

Metadata Update from @spichugi:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

2 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/4013

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

a year ago

Login to comment on this ticket.