Skip to content

Time synch note #875

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

Merged
Feediver1 merged 3 commits into from
Dec 3, 2024
Merged

Time synch note #875

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b20a0c4
new note
Feediver1 Nov 22, 2024
44bb0dc
Update modules/develop/pages/produce-data/configure-producers.adoc
Feediver1 Dec 3, 2024
b973217
Merge branch 'main' into Docs-20
Feediver1 Dec 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions modules/develop/pages/produce-data/configure-producers.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -217,6 +217,8 @@ in one place, while also enabling features like schema evolution.

Redpanda employs a unique strategy to help ensure the accuracy of retention operations. In this strategy, closed segments are only eligible for deletion when the age of all messages in the segment exceeds a configured threshold. However, when a producer sends a message to a topic, the timestamp set by the producer may not accurately reflect the time the message reaches the broker. To address this time skew, each time a producer sends a message to a topic, Redpanda records the broker's system date and time in the `broker_timestamp` property of the message. This property helps maintain accurate retention policies, even when the message's creation timestamp deviates from the broker's time.

NOTE: Clock synchronization should be monitored by the server owner, as Redpanda does not monitor clock synchronization. While Redpanda does not rely on clocks for correctness, if you are using `LogAppendTime` (server timestamp set by Redpanda), server clocks may affect the time your application sees.

ifndef::env-cloud[]
See also:

Expand Down
Loading