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

Add nsState healthcheck if remote offset starts to approach 24 hours #3812

Closed

389-ds-bot opened this issue Sep 13, 2020 · 2 comments

Labels

closed: duplicate

Milestone

389-ds-bot commented Sep 13, 2020

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50757

Created at 2019-12-02 22:43:08 by mreynolds (@mreynolds389)
Closed at 2019-12-04 04:05:09 as duplicate
Assigned to nobody

Issue Description

Report a healthcheck error if the remote offset reported in nsState is getting close to 24 hours - which would trigger replication time skew errors.

389-ds-bot added the closed: duplicate label

389-ds-bot added this to the 1.4.0 milestone

389-ds-bot closed this as completed

Author

389-ds-bot commented Sep 13, 2020

Comment from mreynolds (@mreynolds389) at 2019-12-04 04:05:10

Handling this in issue 50747

Author

389-ds-bot commented Sep 13, 2020

Comment from mreynolds (@mreynolds389) at 2019-12-04 04:05:10

Metadata Update from @mreynolds389:

Custom field origin adjusted to None
Custom field reviewstatus adjusted to None
Issue close_status updated to: duplicate
Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment