Re: Sequence rollover; local offset updated

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

 



Hi Christophe,

Like William said the message "csngen_new_csn - Sequence rollover; local offset updated." is not alarming and IMHO are likely related to the NTP update.

The sequence number (seq_num) is a sub second counter increased for each write operation. It can also jump ahead to a seq_num value of a received replicated update. In short if a replica timestamps an update with a high seq_num, this high seq_num will be propagated to the others replica. It looks not realistic to process 65K updates in the same second. So the only thing I can think of is a jump of system time (ahead and/or backward) on one of the replica. This jump can be transient.

If such jump occurred, the next CSNs will be timestamped with the same second but this timestamp will last longer than an actual second. In such case we can process many writes, timestamped in the same second, increasing only the sequence number.

The NTP update,  likely triggered a jump. This jump was consumed by the regular clock ticking. During this period, seq_num rollover several times. Then when the jump was totally consumed, seq_num reset at each change of second and no longer rollover.

best regards
thierry
On 2/6/20 1:09 AM, Christophe Trefois wrote:
Dear @William

Thank you a lot for this nice answer and explanations.

We did update and harmonise the ntp server of all 8 FreeIPA servers that we have and continued to see a lot of these errors above over the next couple weeks.

However, since 10 days ago, all messages of this sort stopped and have not yet returned.

Is there some catch up mechanism that somehow was able to "heal" ?

Thanks a lot for your insights,
Christophe
_______________________________________________
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
_______________________________________________
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




[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