Re: Determining max CSN of running server

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



there was an old RHEL-7.4 and RHEL-7.5 issue and fix in 
1.3.5.10-20 replication halt - pending list first CSN not committed, pending list increasing
https://bugzilla.redhat.com/1460070
https://github.com/389ds/389-ds-base/issues/2346
but you have a (somehow) more recent version, 389-ds-base-1.3.10.2-10.el7_9.x86_64 ( and one 389-ds-base-1.3.11.1-1.el7_9.x86_6 ) , so this should be fixed.
the issue could have been related to sub operations.
the logs provided do show a replica with a large and growing pending list, taking several seconds to parse (in double digits).
and in this particular replication agreement, the consumer's max CSN is higher than the local supplier's one, so the remote replica/consumer is flagged as "ignored"
then later in time some updates go through as the RUV in the R.A. have been updated by a better knowledgeable replica.
but this seems to repeat (strange)
I want to suggest deleting the changelog, and re-init that replica, but maybe Thierry or Pierre or William B. have a better suggestion.
M.



On Thu, Feb 29, 2024 at 2:21 PM William Faulk <d4hgcdgdmj@xxxxxxxxxxxxxx> wrote:
> FYI: There is a list of pending operations to ensure that the RUV is not
> updated while an older operation is not yet completed. And I suspect that
> you hit a bug about this list. I remember that we fixed something in that
> area a few years ago ...

I think I found it, or something closely related.

https://github.com/389ds/389-ds-base/pull/4553
--
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux