1 views collected around this technical thread.
This article explains the core components and advantages of Chrony, compares it with ntpd, and provides step‑by‑step configuration and verification commands for deploying Chrony as both NTP client and server on Linux systems.
The article explains WebRTC audio‑video synchronization by detailing the ITU‑R BT.1359‑1 standard, describing a synchronizer that computes target delays from desired and packet‑pair delays, applying bounded adjustments via sliding‑average filtering, and outlining a hardware method for measuring resulting latency.
This article walks through a real‑world OceanBase NTP clock desynchronization problem, demonstrating how the ChatDBA AI assistant guides four rounds of interactive troubleshooting, identifies misconfigured ntpdate‑wrapper scripts, and provides a concrete solution to restore proper time sync.
The International Earth Rotation Service’s decision to skip the 2024 leap second and ultimately abolish leap seconds by 2035 relieves programmers of complex time‑keeping hacks, as current NTP, PTP, and newer Windows systems can already handle adjustments while past leap seconds have repeatedly disrupted software.
The article explains why leap seconds are added to keep UTC aligned with Earth's rotation, describes the three time scales (UT1, TAI, UTC), details Linux kernel bugs caused by leap‑second handling across various versions, and offers mitigation scripts while discussing the future removal of leap seconds.
This article analyzes a production incident where duplicate IDs were generated by the Snowflake algorithm due to server clock rollback, explains the algorithm's structure and pitfalls, and presents several open‑source solutions such as Meituan Leaf, Baidu UidGenerator, and Redis for reliable distributed ID generation.
This article explores the origins of time measurement, the transition from astronomical clocks to atomic standards, how UTC and leap seconds are defined, and the technical mechanisms—especially NTP—that keep computers and devices precisely synchronized across the globe.
The article explains the historical definition of the second, the concept of leap seconds, their impact on large‑scale IT systems, and details Alibaba's multi‑step approach of splitting the extra second into 86,400 parts to maintain accurate time synchronization across its infrastructure.
The article explains the concept of a leap second, its scheduling by the IERS, the operational impact on large IT systems, and details Alibaba's technical strategy—including testing, time‑distribution methods, and team coordination—to guarantee a seamless transition during the 2015 positive leap second.